rationalize-deps
Analyze Cargo.toml dependencies and attempt to remove unused features to reduce compile times and binary size
Install with Tessl CLI
npx tessl i github:quickwit-oss/tantivy --skill rationalize-deps74
Quality
72%
Does it follow best practices?
Impact
62%
1.40xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/rationalize-deps/SKILL.mdDiscovery
67%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 effectively communicates specific actions and outcomes within a well-defined niche (Rust/Cargo dependency optimization). However, it lacks explicit trigger guidance ('Use when...') and could benefit from additional natural keywords users might employ when seeking this functionality.
Suggestions
Add a 'Use when...' clause with trigger scenarios like 'Use when optimizing Rust projects, reducing crate bloat, or when the user mentions slow compile times'
Include additional natural keywords users might say: 'Rust', 'crate', 'cargo build', 'optimize dependencies', 'feature flags'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Analyze Cargo.toml dependencies' and 'remove unused features' with clear outcomes 'reduce compile times and binary size'. | 3 / 3 |
Completeness | Clearly answers 'what' (analyze dependencies, remove unused features) but lacks an explicit 'Use when...' clause to guide Claude on when to select this skill. | 2 / 3 |
Trigger Term Quality | Includes good keywords like 'Cargo.toml', 'dependencies', 'features', 'compile times', 'binary size', but missing common variations users might say like 'Rust', 'crate', 'bloat', or 'optimize'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Cargo.toml' is highly specific to Rust ecosystem, and the focus on 'unused features' for compile/binary optimization creates a clear, distinct niche unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, actionable skill with clear workflows and validation steps for dependency rationalization. The main weaknesses are minor verbosity in the overview and lack of progressive disclosure to external files for the common patterns and detailed reference material. The executable commands and concrete examples make it immediately usable.
Suggestions
Trim the overview section - remove explanatory text like 'Many crates enable features by default' and just list what the skill does
Consider extracting 'Common Patterns' to a separate PATTERNS.md file and linking to it for cleaner progressive disclosure
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary explanation (e.g., 'Many crates enable features by default that may not be needed'). The overview section could be trimmed, and some steps have redundant context. | 2 / 3 |
Actionability | Provides fully executable commands (cargo tree, cargo check, cargo metadata with jq), concrete TOML examples showing before/after configurations, and specific patterns for common crates like serde, tokio, and reqwest. | 3 / 3 |
Workflow Clarity | Clear 5-step sequence with explicit validation checkpoints (Step 3c: cargo check, Step 5: full verification). Includes feedback loops for error recovery (read errors, add features, re-run) and a rollback section for error recovery. | 3 / 3 |
Progressive Disclosure | Content is reasonably structured with clear sections, but everything is inline in a single file. The 'Common Patterns' section could be split to a separate reference file, and there are no external references for deeper exploration. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.