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
89
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 distinctive. However, it reads more like a keyword dump than a proper skill description - it lacks concrete action statements about what the skill actually does and doesn't follow the recommended 'Use when...' structure for explicit trigger guidance.
Suggestions
Add a clear capability statement at the start describing concrete actions (e.g., 'Debug Rust compiler errors, explain ownership/borrowing concepts, design async patterns, review Rust code')
Restructure with an explicit 'Use when...' clause to separate capabilities from trigger conditions
Condense the trigger term list - many are redundant (e.g., 'compile error' appears twice, '编译错误' and 'compile error' are duplicates)
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Rust) and mentions some actions like 'errors, design, and coding' but doesn't list concrete specific actions like 'debug borrow checker errors' or 'implement async patterns'. It's more focused on trigger terms than describing what the skill actually does. | 2 / 3 |
Completeness | The 'what' is weak - only vaguely states 'ALL Rust questions including errors, design, and coding'. The 'when' is addressed through extensive trigger terms but lacks an explicit 'Use when...' clause. The description is essentially a keyword list rather than a structured explanation. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say, including bilingual triggers (Chinese/English), specific error codes (E0382, E0597), common error messages ('value moved', 'cannot borrow'), tools (cargo, rustc, tokio), and question patterns ('how to use', '怎么用'). | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused specifically on Rust programming with highly specific triggers like Rust error codes, Rust-specific concepts (borrow checker, ownership, lifetimes), and Rust tooling (cargo, rustc, Cargo.toml). 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 uses tables effectively for quick lookup, provides clear cognitive frameworks for ambiguous cases, 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 decision logic is explicit with clear if-then mappings. | 3 / 3 |
Workflow Clarity | The cognitive layer framework provides a clear decision sequence (identify layer → load skill → trace → cross-reference → answer). The priority hierarchy explicitly orders conflict resolution, and the negotiation protocol has clear trigger conditions. | 3 / 3 |
Progressive Disclosure | Excellent structure with overview tables in the main file and clear references to sub-files (patterns/negotiation.md, examples/workflow.md, integrations/os-checker.md). All references are one level deep and clearly signaled. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 12 / 16 Passed | |
- 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.