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, 智能指针, 引用计数, 堆分配

Quality

78%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/m02-resource/SKILL.md

Quality

Discovery

72%

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 description excels at trigger term coverage with comprehensive keywords including type names, concepts, common questions, and multilingual support. However, it lacks specificity about what actions the skill actually performs (teaching, comparing, debugging?) and would benefit from an explicit 'Use when...' clause to improve completeness.

Suggestions

Add concrete actions describing what the skill does, e.g., 'Explains smart pointer selection, demonstrates ownership patterns, helps debug memory issues'

Convert the 'Triggers:' list format into a proper 'Use when...' clause, e.g., 'Use when users ask about Box, Rc, Arc, or need help choosing between smart pointer types'

Dimension	Reasoning	Score
Specificity	Names the domain (smart pointers and resource management) and lists specific types (Box, Rc, Arc, etc.), but doesn't describe concrete actions like 'explains when to use', 'helps choose between', or 'demonstrates patterns'.	2 / 3
Completeness	The 'when' is partially addressed through the 'Triggers:' list and 'CRITICAL: Use for' prefix, but lacks an explicit 'Use when...' clause explaining the scenarios. The 'what' is weak - it doesn't clearly state what actions the skill performs.	2 / 3
Trigger Term Quality	Excellent coverage of natural terms including type names (Box, Rc, Arc, RefCell, Cell), concepts (heap allocation, reference counting, RAII), common user questions ('should I use Box or Rc', 'when to use Arc vs Rc'), and even Chinese translations (智能指针, 引用计数).	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with specific Rust smart pointer types and concepts that wouldn't overlap with other skills. The combination of type names, concepts, and comparison questions creates a clear niche.	3 / 3
	Total	10 / 12 Passed

Implementation

85%

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 decision-making skill that excels at guiding smart pointer selection through clear flowcharts, tables, and trace patterns. The content is highly concise and assumes appropriate Rust knowledge. The main weakness is the lack of executable code examples—while the decision guidance is excellent, adding 2-3 concrete code snippets would make it more immediately actionable.

Suggestions

Add 2-3 minimal executable code examples showing common patterns (e.g., Rc<RefCell<T>> usage, breaking a cycle with Weak)

Include a brief code snippet in the 'Common Errors' section showing the RefCell panic scenario and the try_borrow fix

Dimension	Reasoning	Score
Conciseness	Extremely lean and efficient. Uses tables, flowcharts, and minimal prose. No unnecessary explanations of what smart pointers are—assumes Claude knows Rust fundamentals and focuses purely on decision-making guidance.	3 / 3
Actionability	Provides clear decision frameworks and type mappings, but lacks executable code examples. The flowcharts and tables guide decisions well, but there are no copy-paste ready code snippets showing actual usage patterns.	2 / 3
Workflow Clarity	The decision flowchart provides an unambiguous sequence for choosing the right smart pointer. The 'Trace Up/Down' sections create clear navigation paths. For a decision-making skill (not a multi-step operation), the workflow is exceptionally clear.	3 / 3
Progressive Disclosure	Well-organized with clear sections progressing from core questions to quick reference to detailed decisions. Related skills are clearly signaled with one-level-deep references. Content is appropriately structured for a skill file.	3 / 3
	Total	11 / 12 Passed

Validation

90%

Warnings & errors only

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: 1f4becd

Reviewed: 19 days ago

Table of Contents

Discovery Implementation Validation

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.