SkillAgentSearch skills...

m01-ownership

CRITICAL: Use for ownership/borrow/lifetime issues. Triggers: E0382, E0597, E0506, E0507, E0515, E0716, E0106, value moved, borrowed value does not live long enough, cannot move out of, use of moved value, ownership, borrow, lifetime, 'a, 'static, move, clone, Copy, 所有权, 借用, 生命周期

Install / Use

npx skills add actionbook/rust-skills --skill m01-ownership

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

87/100

Supported Platforms

Universal

Tags

Our assessment of m01-ownership

m01-ownership scores 87/100 on our quality scale, 2169th of 4,698 Development & Engineering skills we index (top 47%).

Its SKILL.md is 4.0 KB long, well organised into 10 sections with 2 code examples: a solid amount of guidance for an agent.

With 1,479 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
18/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 3 months ago, so m01-ownership is actively maintained.
  • Our last check on 2026-11-02 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-03. Automated pattern scan on 2026-10-03. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

m01-ownership compared with similar skills

All 4 of these similar skills score higher than m01-ownership; compare them before choosing.

SkillScoreStarsUpdatedFormat
m01-ownership (this skill)by actionbook871.5k3mo agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
lobehubby lobehub10085.6ktodayMCP Server

Frequently asked questions

How do I install m01-ownership?
Run npx skills add actionbook/rust-skills --skill m01-ownership. The install tabs above show the steps for each supported agent.
Which AI agents does m01-ownership work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is m01-ownership safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is m01-ownership still maintained?
The repository was last updated about 3 months ago, so m01-ownership is actively maintained.

name: m01-ownership description: "CRITICAL: Use for ownership/borrow/lifetime issues. Triggers: E0382, E0597, E0506, E0507, E0515, E0716, E0106, value moved, borrowed value does not live long enough, cannot move out of, use of moved value, ownership, borrow, lifetime, 'a, 'static, move, clone, Copy, 所有权, 借用, 生命周期" user-invocable: false

Ownership & Lifetimes

Layer 1: Language Mechanics

Core Question

Who should own this data, and for how long?

Before fixing ownership errors, understand the data's role:

  • Is it shared or exclusive?
  • Is it short-lived or long-lived?
  • Is it transformed or just read?

Error → Design Question

| Error | Don't Just Say | Ask Instead | |-------|----------------|-------------| | E0382 | "Clone it" | Who should own this data? | | E0597 | "Extend lifetime" | Is the scope boundary correct? | | E0506 | "End borrow first" | Should mutation happen elsewhere? | | E0507 | "Clone before move" | Why are we moving from a reference? | | E0515 | "Return owned" | Should caller own the data? | | E0716 | "Bind to variable" | Why is this temporary? | | E0106 | "Add 'a" | What is the actual lifetime relationship? |


Thinking Prompt

Before fixing an ownership error, ask:

  1. What is this data's domain role?

    • Entity (unique identity) → owned
    • Value Object (interchangeable) → clone/copy OK
    • Temporary (computation result) → maybe restructure
  2. Is the ownership design intentional?

    • By design → work within constraints
    • Accidental → consider redesign
  3. Fix symptom or redesign?

    • If Strike 3 (3rd attempt) → escalate to Layer 2

Trace Up ↑

When errors persist, trace to design layer:

E0382 (moved value)
    ↑ Ask: What design choice led to this ownership pattern?
    ↑ Check: m09-domain (is this Entity or Value Object?)
    ↑ Check: domain-* (what constraints apply?)

| Persistent Error | Trace To | Question | |-----------------|----------|----------| | E0382 repeated | m02-resource | Should use Arc/Rc for sharing? | | E0597 repeated | m09-domain | Is scope boundary at right place? | | E0506/E0507 | m03-mutability | Should use interior mutability? |


Trace Down ↓

From design decisions to implementation:

"Data needs to be shared immutably"
    ↓ Use: Arc<T> (multi-thread) or Rc<T> (single-thread)

"Data needs exclusive ownership"
    ↓ Use: move semantics, take ownership

"Data is read-only view"
    ↓ Use: &T (immutable borrow)

Quick Reference

| Pattern | Ownership | Cost | Use When | |---------|-----------|------|----------| | Move | Transfer | Zero | Caller doesn't need data | | &T | Borrow | Zero | Read-only access | | &mut T | Exclusive borrow | Zero | Need to modify | | clone() | Duplicate | Alloc + copy | Actually need a copy | | Rc<T> | Shared (single) | Ref count | Single-thread sharing | | Arc<T> | Shared (multi) | Atomic ref count | Multi-thread sharing | | Cow<T> | Clone-on-write | Alloc if mutated | Might modify |

Error Code Reference

| Error | Cause | Quick Fix | |-------|-------|-----------| | E0382 | Value moved | Clone, reference, or redesign ownership | | E0597 | Reference outlives owner | Extend owner scope or restructure | | E0506 | Assign while borrowed | End borrow before mutation | | E0507 | Move out of borrowed | Clone or use reference | | E0515 | Return local reference | Return owned value | | E0716 | Temporary dropped | Bind to variable | | E0106 | Missing lifetime | Add 'a annotation |


Anti-Patterns

| Anti-Pattern | Why Bad | Better | |--------------|---------|--------| | .clone() everywhere | Hides design issues | Design ownership properly | | Fight borrow checker | Increases complexity | Work with the compiler | | 'static for everything | Restricts flexibility | Use appropriate lifetimes | | Leak with Box::leak | Memory leak | Proper lifetime design |


Related Skills

| When | See | |------|-----| | Need smart pointers | m02-resource | | Need interior mutability | m03-mutability | | Data is domain entity | m09-domain | | Learning ownership concepts | m14-mental-model |

Related Skills

View on GitHub
GitHub Stars1.5k
CategoryDevelopment
Updated2mo ago
Forks114

Languages

Shell

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium