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

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/rust-router/SKILL.md

Quality

Content

62%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, mostly lean routing map with a clear prioritized workflow, but it leans on tabular lookups for actionability and references bundle files that are not present in the skill package.

Suggestions

Ship the referenced sub-files (patterns/negotiation.md, examples/workflow.md, integrations/os-checker.md) or remove the Sub-Files Reference table so progressive disclosure is not broken.

Add a brief, concrete example of a routed query (input → layer → skill) so actionability goes beyond table lookup.

Trim the meta-cognition ASCII framework if it is not directly used in routing, to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean routing tables with minimal concept re-explanation; the main verbosity is the meta-cognition framework ASCII diagram and overlapping routing tables, but it generally assumes Claude's competence and earns its tokens.	4 / 5
Actionability	It gives concrete routing destinations and an explicit default Cargo.toml, but as a router skill its guidance is largely tabular lookups rather than executable steps; the sub-files it points to are not present, so execution depends on missing bundles.	3 / 5
Workflow Clarity	The Priority Order section gives a clear 5-step sequence with a priority hierarchy and keyword-conflict resolution table; this is a routing (not destructive) skill so the batch/destruction cap does not apply, and checkpoints are implicit but the sequence is coherent.	4 / 5
Progressive Disclosure	It signals one-level-deep references (patterns/negotiation.md, examples/workflow.md, integrations/os-checker.md) in a Sub-Files table, but those bundle directories (references/scripts/assets) are absent, so the referenced paths cannot be verified and the structure is incomplete.	3 / 5
	Total	14 / 20 Passed

Description

65%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description excels at trigger-term coverage but is overbroad ('ALL Rust questions') and action-thin, hurting both specificity and conflict risk. It states when to trigger clearly but only weakly conveys what the skill actually does.

Suggestions

Replace 'Use for ALL Rust questions' with a scoped statement of the concrete action (e.g., 'Routes Rust questions to specialized sub-skills based on error codes and domain keywords') to improve specificity and reduce conflict risk.

State the 'what' explicitly in third person ('Routes...', 'Classifies...') rather than relying solely on trigger keyword lists.

Narrow the trigger scope so it does not claim every Rust question, which conflicts with the numerous sibling m0x/domain skills it references.

Dimension	Reasoning	Score
Specificity	It names the Rust domain and many trigger keywords, but describes almost no concrete actions the skill performs (it merely lists trigger terms and 'Use for ALL Rust questions'); actions are minimal/generic relative to the anchor.	2 / 5
Completeness	It has an explicit 'when' (CRITICAL: Use for ALL Rust questions; Triggers on...) and an implied 'what' (routing Rust questions), but the 'what' is thin — it lists triggers rather than stating concretely what the skill does (routes/categorizes Rust questions to sub-skills).	4 / 5
Trigger Term Quality	Comprehensive bilingual coverage of natural terms users say — error codes (E0382, E0597), concepts (ownership, borrow, lifetime, async, tokio), and phrasings (how to use, 为什么, what is) — across English and Chinese synonyms.	5 / 5
Distinctiveness Conflict Risk	The claim 'Use for ALL Rust questions' is extremely broad, creating high overlap/conflict risk with any other Rust-related skill (m01-m07, domain-* skills alluded to in the body); it would fire on virtually any Rust query.	2 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: actionbook/rust-skills
Path: skills/rust-router/SKILL.md
Commit: 5c40d3a

Reviewed: 14 days ago

Table of Contents

Discovery Implementation Validation

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.