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, 所有权, 借用, 生命周期
67
81%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description with excellent trigger term coverage and clear distinctiveness for Rust ownership/borrow/lifetime debugging. Its main weakness is that it could be more specific about what concrete actions it performs (e.g., diagnosing errors, suggesting fixes, refactoring code). The comprehensive list of error codes, error messages, and multilingual keywords makes it highly effective for skill selection.
Suggestions
Add specific concrete actions like 'Diagnoses borrow checker errors, suggests lifetime annotations, recommends refactoring to resolve move/clone issues' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (ownership/borrow/lifetime issues) and implies the action (diagnosing/fixing Rust compiler errors), but doesn't list specific concrete actions like 'diagnose borrow checker errors, suggest lifetime annotations, refactor code to avoid moves'. | 2 / 3 |
Completeness | Clearly answers both 'what' (handles ownership/borrow/lifetime issues) and 'when' (explicit 'Triggers:' clause with comprehensive list of error codes, error messages, and keywords that should activate this skill). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including specific error codes (E0382, E0597, etc.), exact compiler error messages ('value moved', 'borrowed value does not live long enough'), Rust-specific keywords ('ownership', 'borrow', 'lifetime', 'clone', 'Copy', ''a', ''static'), and even Chinese translations (所有权, 借用, 生命周期). | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche — Rust ownership/borrowing/lifetime errors are a very specific domain. The specific error codes and Rust-specific terminology make it extremely unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise skill that takes a thoughtful design-thinking approach to Rust ownership errors rather than just listing mechanical fixes. Its main weakness is the lack of concrete, executable code examples — for a skill triggered by specific compiler errors, showing actual Rust code that causes each error and the corrected version would make it significantly more actionable. The progressive disclosure and cross-referencing to related skills is excellent.
Suggestions
Add concrete before/after Rust code examples for the most common errors (E0382, E0597, E0515) showing the broken code and the fix, to improve actionability from guidance-level to executable-level.
Add an explicit diagnostic workflow sequence: e.g., '1. Identify error code → 2. Check Error Code Reference table → 3. Apply Thinking Prompt questions → 4. Attempt fix → 5. If 3rd attempt fails, Trace Up to design layer' to make the multi-step process unambiguous.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It uses tables extensively to compress information, avoids explaining what Rust ownership/borrowing is (assumes Claude knows), and every section serves a clear purpose. No unnecessary padding or concept explanations. | 3 / 3 |
Actionability | The skill provides structured decision-making guidance and quick-fix tables, but lacks executable code examples. For a skill triggered by specific compiler errors, concrete before/after code snippets showing how to fix each error pattern would significantly improve actionability. | 2 / 3 |
Workflow Clarity | The 'Thinking Prompt' section provides a reasonable decision sequence, and the 'Strike 3' escalation is a useful checkpoint. However, the workflow for actually diagnosing and fixing errors is implicit rather than explicit — there's no clear step-by-step process like 'identify error → check table → apply thinking prompt → attempt fix → if fails, trace up.' | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections progressing from core concepts to error reference to anti-patterns. References to related skills (m02-resource, m03-mutability, m09-domain, m14-mental-model) are clearly signaled and one level deep. The 'Trace Up/Down' pattern effectively creates navigation without nesting. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- actionbook/rust-skills
- Commit
fa60f79
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.