m06-error-handling
CRITICAL: Use for error handling. Triggers: Result, Option, Error, ?, unwrap, expect, panic, anyhow, thiserror, when to panic vs return Result, custom error, error propagation, 错误处理, Result 用法, 什么时候用 panic
88
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
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 Rust-specific keywords and multilingual support, making it highly discoverable. However, it lacks explicit action verbs describing what the skill does and uses a 'Triggers:' format rather than a proper 'Use when...' clause, reducing clarity about the skill's actual capabilities.
Suggestions
Add concrete action verbs describing capabilities, e.g., 'Guides implementation of error handling patterns, custom error types, and error propagation strategies in Rust.'
Replace 'Triggers:' list format with a proper 'Use when...' clause, e.g., 'Use when implementing error handling, choosing between Result and panic, or working with anyhow/thiserror crates.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (error handling) and lists relevant types/concepts (Result, Option, Error, unwrap, expect, panic, anyhow, thiserror), but doesn't describe concrete actions like 'implement custom error types' or 'convert between error types'. | 2 / 3 |
Completeness | The 'what' is implied (error handling guidance) but not explicitly stated with concrete actions. The 'when' is provided via 'Triggers:' list but lacks an explicit 'Use when...' clause explaining the selection criteria. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: includes Rust-specific keywords (Result, Option, unwrap, expect, panic), popular crates (anyhow, thiserror), common questions ('when to panic vs return Result'), and even Chinese translations (错误处理, Result 用法). | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Rust-specific terminology (Result, Option, anyhow, thiserror, unwrap) that clearly separates it from general programming or other language error handling skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that efficiently teaches Rust error handling through decision-focused guidance rather than concept explanation. The structure moves from core questions through decision flowcharts to concrete patterns, with clear cross-references to related skills. The use of tables maximizes information density while maintaining clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Uses tables and flowcharts to convey maximum information with minimal tokens. No unnecessary explanations of concepts Claude already knows - assumes competence with Rust fundamentals. | 3 / 3 |
Actionability | Provides concrete, executable patterns with specific code examples (Result signatures, ?, .context()). The decision flowchart and quick reference tables give copy-paste ready patterns for immediate use. | 3 / 3 |
Workflow Clarity | The 'Thinking Prompt' section provides a clear 3-step decision process. The decision flowchart explicitly sequences the thought process with clear branching logic. For a conceptual skill about error handling strategy, this is appropriately structured. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from core concepts to implementation details. References to related skills (m13-domain-error, m11-ecosystem, etc.) are one level deep and clearly signaled in the 'Related Skills' and 'Trace Up/Down' sections. | 3 / 3 |
Total | 12 / 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
1f4becd
- 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.