CtrlK
BlogDocsLog inGet started
Tessl Logo

m02-resource

CRITICAL: Use for smart pointers and resource management. Triggers: Box, Rc, Arc, Weak, RefCell, Cell, smart pointer, heap allocation, reference counting, RAII, Drop, should I use Box or Rc, when to use Arc vs Rc, 智能指针, 引用计数, 堆分配

63

Quality

79%

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/m02-resource/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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-organized, knowledge-respecting decision reference for Rust smart pointers with concrete type-selection guidance and a clear flowchart. It is held back by heavy cross-table redundancy and a monolithic inline structure with no progressive split.

Suggestions

Consolidate the repeated Weak-for-cycle / Rc-leak guidance that appears in five sections into a single authoritative spot to reduce token cost.

Add one or two minimal executable Rust snippets (e.g. Arc<RefCell<T>> usage, a Weak upgrade) to lift actionability from guidance to copy-paste ready.

Split the Quick Reference / Common Errors / Anti-Patterns tables into a separate reference file referenced from SKILL.md to enable progressive disclosure.

DimensionReasoningScore

Conciseness

Assumes Claude's knowledge (no explanation of what smart pointers or Rust are) and uses dense tables, but the Weak-for-cycle guidance recurs across Error→Design, Thinking Prompt, Trace Down, Quick Reference, Common Errors, and Anti-Patterns, adding redundant tokens.

4 / 5

Actionability

Provides concrete mappings (e.g. 'Need shared mutable data → Rc<RefCell<T>>', 'Multi-thread → Arc<Mutex<T>>') and an executable decision flowchart; as an instruction-only skill it lacks code snippets but the guidance is specific and actionable.

4 / 5

Workflow Clarity

The numbered Thinking Prompt (1→2→3) and ASCII decision flowchart give a clear sequenced decision path; no destructive or batch operations apply, so the level-3 cap is not triggered, but there is no error-recovery feedback loop.

4 / 5

Progressive Disclosure

Well-sectioned with clear headers but entirely monolithic — all ~150 lines of reference tables sit inline in SKILL.md with no external references, and overlapping tables (Quick Reference, Common Errors, Anti-Patterns) could be consolidated or split.

3 / 5

Total

15

/

20

Passed

Description

77%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 strong, trigger-rich description with comprehensive natural and multilingual keywords and clear distinctiveness. Its main weakness is that it states the domain to use rather than the concrete actions the skill performs.

Suggestions

Replace the generic 'Use for smart pointers and resource management' opening with concrete verbs describing what the skill does (e.g., 'Guides selection of Rust smart pointers (Box/Rc/Arc/Weak/RefCell) based on ownership, threading, and cycle constraints').

Keep the strong Triggers list; it already answers 'when' well.

DimensionReasoningScore

Specificity

Names the domain and many concrete entities (Box, Rc, Arc, Weak, RefCell, Cell, RAII, Drop) but frames them as 'Use for' targets rather than concrete skill actions, matching the 'names domain, actions minimal/generic' band just above level 2.

3 / 5

Completeness

Both 'what' (smart pointers and resource management) and 'when' (explicit 'Triggers:' list plus 'Use for') are present, but the 'what' is a domain label rather than concrete actions, keeping it below the fully explicit level 5.

4 / 5

Trigger Term Quality

Comprehensive coverage spanning technical jargon (Box, Rc, Arc, RAII, reference counting), natural user phrasings ('should I use Box or Rc', 'when to use Arc vs Rc'), and Chinese synonyms (智能指针, 引用计数, 堆分配).

5 / 5

Distinctiveness Conflict Risk

Smart pointers form a clear niche with distinct triggers (Box, Rc, Arc, RefCell), with only minor overlap risk against sibling skills like m01-ownership and m03-mutability.

4 / 5

Total

16

/

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.

Validation — 16 / 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.