m04-zero-cost
CRITICAL: Use for generics, traits, zero-cost abstraction. Triggers: E0277, E0308, E0599, generic, trait, impl, dyn, where, monomorphization, static dispatch, dynamic dispatch, impl Trait, trait bound not satisfied, 泛型, 特征, 零成本抽象, 单态化
77
72%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/m04-zero-cost/SKILL.mdQuality
Discovery
44%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 error codes, making it highly discoverable and distinctive. However, it critically fails to describe what the skill actually does - there are no action verbs or capability statements explaining how it helps users with these concepts.
Suggestions
Add concrete action verbs describing capabilities, e.g., 'Diagnoses and resolves Rust generic/trait errors, explains type system concepts, suggests trait bound fixes'
Convert the 'Triggers:' format to a proper 'Use when...' clause, e.g., 'Use when encountering compiler errors E0277, E0308, E0599 or when working with generics, traits, or type bounds'
Ensure third-person voice with explicit capability statements rather than just listing topics
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lacks concrete actions entirely. It only says 'Use for generics, traits, zero-cost abstraction' without describing what the skill actually does (e.g., 'diagnoses', 'fixes', 'explains'). | 1 / 3 |
Completeness | The 'what' is extremely weak - it never explains what actions the skill performs. While it has a 'Triggers:' section implying when to use it, there's no explicit 'Use when...' clause and the capability description is absent. | 1 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including error codes (E0277, E0308, E0599), technical concepts (generic, trait, impl, dyn, where), and even multilingual terms (泛型, 特征). Users would naturally use these terms when encountering Rust generics issues. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific Rust error codes and domain-specific terminology. The combination of error codes like E0277 and concepts like 'monomorphization' and 'trait bound not satisfied' creates a clear, non-conflicting niche. | 3 / 3 |
Total | 8 / 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 exemplary skill document that maximizes information density through effective use of tables and structured decision guides. It transforms error codes into design questions rather than just fixes, demonstrating sophisticated pedagogical approach. The content is highly actionable with concrete syntax examples while maintaining excellent organization and cross-referencing.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Uses tables extensively to compress information, no unnecessary explanations of concepts Claude already knows, and every section delivers actionable value without padding. | 3 / 3 |
Actionability | Provides concrete, executable Rust syntax examples, clear decision tables with specific scenarios, and direct error code mappings to fixes. The syntax comparison section is copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear decision flows with 'Trace Up' and 'Trace Down' sections that guide through the thought process. The 'Error → Design Question' table transforms error handling into a structured diagnostic workflow. | 3 / 3 |
Progressive Disclosure | Well-organized with clear section headers, appropriate use of tables for reference material, and explicit cross-references to related skills (m05, m09, m10, m07) without deep nesting. | 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.