m05-type-driven
CRITICAL: Use for type-driven design. Triggers: type state, PhantomData, newtype, marker trait, builder pattern, make invalid states unrepresentable, compile-time validation, sealed trait, ZST, 类型状态, 新类型模式, 类型驱动设计
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 keywords including technical Rust patterns and multilingual support. However, it reads more like a keyword list than a proper description - it lacks concrete action verbs explaining what the skill actually does. The 'CRITICAL' prefix and 'Triggers:' format is unconventional but functional for skill selection.
Suggestions
Add concrete action verbs describing what the skill does, e.g., 'Implements type-safe patterns, refactors code to use type states, designs APIs that prevent invalid states at compile time.'
Restructure to follow the recommended format: '[What it does]. Use when [triggers].' rather than a keyword dump.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (type-driven design) and lists specific patterns/concepts (type state, PhantomData, newtype, marker trait, builder pattern), but doesn't describe concrete actions - it's more a list of concepts than actions the skill performs. | 2 / 3 |
Completeness | The 'when' is partially addressed with 'CRITICAL: Use for type-driven design' and explicit 'Triggers:' list, but the 'what' is weak - it doesn't explain what actions the skill actually performs (e.g., 'Implements type-safe patterns', 'Refactors code to use type states'). | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms including technical patterns users would search for (PhantomData, newtype, builder pattern, sealed trait, ZST), design principles ('make invalid states unrepresentable', 'compile-time validation'), and even Chinese translations for international users. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with very specific Rust-focused terminology (PhantomData, ZST, sealed trait) that clearly carves out a niche for type-level programming patterns, unlikely to conflict with general coding 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 type-driven design skill that exemplifies concise, actionable documentation. It uses tables effectively for quick lookup, provides executable code examples, and structures content progressively from conceptual questions to concrete patterns. The 'Trace Up/Down' navigation pattern is particularly effective for connecting this skill to related domain concepts.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Uses tables for quick reference, minimal prose, and assumes Claude understands Rust concepts. Every section earns its place with no unnecessary explanation of what newtypes or PhantomData are. | 3 / 3 |
Actionability | Provides executable Rust code examples for key patterns (Newtype, Type State). Decision guides and tables give concrete, copy-paste ready patterns with clear 'Need → Pattern' mappings. | 3 / 3 |
Workflow Clarity | Clear decision flow through 'Thinking Prompt' section with numbered steps. Trace Up/Down sections provide explicit navigation for when to apply patterns. For a conceptual design skill, the workflow is appropriately structured. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from core question → error patterns → thinking prompts → quick reference → examples → decision guide. Related skills section provides one-level-deep references to other skills. | 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.