rust-router
CRITICAL: Use for ALL Rust questions including errors, design, and coding. HIGHEST PRIORITY for: 比较, 对比, compare, vs, versus, 区别, difference, 最佳实践, best practice, tokio vs, async-std vs, 比较 tokio, 比较 async, Triggers on: Rust, cargo, rustc, crate, Cargo.toml, 意图分析, 问题分析, 语义分析, analyze intent, question analysis, compile error, borrow error, lifetime error, ownership error, type error, trait error, value moved, cannot borrow, does not live long enough, mismatched types, not satisfied, E0382, E0597, E0277, E0308, E0499, E0502, E0596, async, await, Send, Sync, tokio, concurrency, error handling, 编译错误, compile error, 所有权, ownership, 借用, borrow, 生命周期, lifetime, 类型错误, type error, 异步, async, 并发, concurrency, 错误处理, error handling, 问题, problem, question, 怎么用, how to use, 如何, how to, 为什么, why, 什么是, what is, 帮我写, help me write, 实现, implement, 解释, explain
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 bilingual keywords and Rust-specific terminology, making it highly discoverable. However, it reads more like a keyword dump than a coherent description, lacking explicit 'Use when...' guidance and specific concrete actions. The description would benefit from restructuring to clearly state what the skill does before listing triggers.
Suggestions
Add an explicit 'Use when...' clause at the beginning that clearly states the selection criteria (e.g., 'Use when the user needs help with Rust programming, debugging compiler errors, or comparing Rust libraries').
Replace vague capability statements like 'ALL Rust questions including errors, design, and coding' with specific concrete actions (e.g., 'Diagnoses compiler errors, explains ownership/borrowing concepts, compares async runtimes, reviews Rust code').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Rust) and mentions some actions like 'errors, design, and coding' and 'questions', but these are broad categories rather than concrete specific actions like 'analyze borrow checker errors' or 'refactor async code'. | 2 / 3 |
Completeness | The 'what' is partially addressed ('ALL Rust questions including errors, design, and coding') but remains vague. The 'when' is implied through extensive trigger terms but lacks an explicit 'Use when...' clause that clearly states selection criteria. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including bilingual keywords (Chinese/English), specific error codes (E0382, E0597), common error messages ('value moved', 'cannot borrow'), tools (cargo, rustc, tokio), and natural question phrases ('how to use', '怎么用', 'why'). | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Rust-specific terminology, error codes, and tools. The combination of 'cargo', 'rustc', 'Cargo.toml', specific error codes like E0382, and Rust concepts like 'borrow checker' creates a clear niche unlikely to conflict with other language 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 exceptionally well-structured routing skill that efficiently guides Claude through a complex decision tree for Rust questions. It excels at using tables for quick lookup, provides clear cognitive frameworks, and appropriately delegates detailed content to sub-files. The skill demonstrates excellent token efficiency while maintaining high actionability.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is highly token-efficient, using tables and structured formats to convey routing logic without unnecessary explanation. It assumes Claude's competence with Rust concepts and doesn't explain what error codes or language features mean. | 3 / 3 |
Actionability | Provides concrete routing tables with specific error codes, keywords, and exact skill file destinations. The Cargo.toml example is copy-paste ready, and the negotiation protocol includes a specific markdown template to follow. | 3 / 3 |
Workflow Clarity | Clear 5-step priority order with explicit sequence. The meta-cognition framework provides a clear decision tree (Layer 1→2→3), and the routing tables serve as unambiguous lookup references for multi-step question handling. | 3 / 3 |
Progressive Disclosure | Excellent structure with a clear overview and well-signaled one-level-deep references to sub-files (patterns/negotiation.md, examples/workflow.md, integrations/os-checker.md). Content is appropriately split between routing logic here and detailed protocols in referenced files. | 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.