CtrlK
BlogDocsLog inGet started
Tessl Logo

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, 所有权, 借用, 生命周期

65

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/m01-ownership/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, token-efficient diagnostic skill that gives actionable design guidance via tables and trace logic rather than rote concept explanation, with only minor redundancy and no bundle files to organize.

Suggestions

Merge or cross-link the 'Error → Design Question' and 'Error Code Reference' tables, which repeat the same error codes with overlapping content.

Add a short concrete code example per common fix (e.g. an E0382 'clone vs redesign' before/after) to lift actionability from guidance to executable.

Make the escalation checkpoint explicit as a validation step (e.g. 'After 3 failed attempts, stop and consult m09-domain before retrying').

DimensionReasoningScore

Conciseness

Lean, table-driven body that assumes Claude knows Rust and avoids explaining what ownership/borrowing is; the only trimmable redundancy is the 'Error → Design Question' and 'Error Code Reference' tables overlapping on the same E0xxx codes.

4 / 5

Actionability

Concrete, specific diagnostic guidance — error→design-question mappings, a pattern→ownership→cost→use-when quick reference (Move, &T, Arc<T>, Cow<T>), and trace-up/down decision trees — fully actionable for an instruction-only skill though it contains no executable code fixes.

4 / 5

Workflow Clarity

Clear sequence (Core Question → Error→Design Question → 3-step Thinking Prompt → Trace Up/Down) with an explicit escalation checkpoint ('If Strike 3 → escalate to Layer 2'); not a 5 because validation/confirmation steps are implicit rather than stated.

4 / 5

Progressive Disclosure

Well-organized single-file overview with clear section headers and one-level cross-skill references (m02-resource, m09-domain) placed appropriately in trace tables and a Related Skills table; no nested references, though at ~135 lines some reference tables could optionally live in a bundle file.

4 / 5

Total

16

/

20

Passed

Description

81%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A trigger-rich, highly distinctive description that excels at 'when to use' via error codes and multilingual keywords, but is weakened by never stating a concrete 'what does this skill do' action.

Suggestions

Lead with a concrete verb phrase stating what the skill does, e.g. 'Diagnose and fix Rust ownership, borrow, and lifetime errors' before the trigger list.

Keep the strong error-code and multilingual trigger list, but consider grouping it (error codes / phrases / keywords) so the 'what' is not buried.

DimensionReasoningScore

Specificity

Names the domain ('ownership/borrow/lifetime issues') and lists many concrete trigger items (error codes, phrases like 'value moved', 'borrowed value does not live long enough'), but describes no concrete actions the skill performs — the only verb is 'Use for'.

3 / 5

Completeness

Explicit and rich 'when' guidance via 'Use for...' plus a 'Triggers:' list, and an implied 'what' (ownership issues), but the 'what' only names the domain rather than stating a concrete action like 'diagnose and fix'.

4 / 5

Trigger Term Quality

Comprehensive natural-term coverage including Rust error codes (E0382, E0597...), compiler phrasings ('cannot move out of', 'use of moved value'), keywords ('move', 'clone', 'Copy', ''a', ''static'), and multilingual synonyms (所有权, 借用, 生命周期).

5 / 5

Distinctiveness Conflict Risk

Clear Rust-ownership niche anchored by specific compiler error codes and lifetime syntax tokens, giving minimal conflict risk with other skills.

5 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
actionbook/rust-skills
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.