rationalize-deps

Analyze Cargo.toml dependencies and attempt to remove unused features to reduce compile times and binary size

1.40x

Quality

72%

Does it follow best practices?

Impact

62%

1.40x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/rationalize-deps/SKILL.md

Quality

Discovery

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 is specific and clearly scoped to a narrow Rust/Cargo optimization task, making it highly distinctive. However, it lacks an explicit 'Use when...' clause which limits completeness, and could benefit from additional trigger terms that users might naturally use when seeking this functionality.

Suggestions

Add a 'Use when...' clause, e.g., 'Use when the user wants to optimize Rust build times, trim Cargo.toml feature flags, or reduce binary size by removing unnecessary dependency features.'

Include additional natural trigger terms like 'Rust', 'crate features', 'build optimization', 'dependency bloat', or 'feature flags' to improve discoverability.

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 does this do' (analyze Cargo.toml dependencies and remove unused features), but lacks an explicit 'Use when...' clause specifying when Claude should select this skill.	2 / 3
Trigger Term Quality	Includes good natural keywords like 'Cargo.toml', 'dependencies', 'unused features', 'compile times', and 'binary size', but misses common variations users might say like 'Rust', 'crate features', 'build optimization', or 'dependency cleanup'.	2 / 3
Distinctiveness Conflict Risk	Very specific niche targeting Cargo.toml feature optimization in Rust projects; unlikely to conflict with other skills due to the narrow domain of unused Cargo feature removal.	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 solid, actionable skill with a well-defined multi-step workflow including validation checkpoints and rollback procedures. The concrete commands and real-world TOML examples make it immediately usable. Minor weaknesses include some unnecessary introductory explanation and the content being slightly monolithic for its length, though neither significantly impacts usability.

Suggestions

Trim the Overview section — the numbered list duplicates the step headings that follow immediately after.

Consider extracting the 'Common Patterns' section into a separate reference file (e.g., COMMON_PATTERNS.md) to keep the main skill leaner and improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Generally efficient but includes some unnecessary explanation (e.g., 'Many crates enable features by default that may not be needed' and the overview section restating what the steps will cover). The common patterns section adds value but the tips section is somewhat generic.	2 / 3
Actionability	Provides concrete, executable commands (cargo tree, cargo metadata with jq, cargo check), specific TOML configuration examples, and real-world patterns for common crates like serde, tokio, and reqwest. The guidance is copy-paste ready.	3 / 3
Workflow Clarity	Clear 5-step sequence with explicit validation checkpoints (cargo check after each change, full workspace verification in Step 5), error recovery feedback loops (read errors → add features → re-check), binary search strategy for complex cases, and a rollback procedure.	3 / 3
Progressive Disclosure	Content is reasonably well-structured with clear sections and headers, but it's all in a single file with no references to supporting materials. The common patterns section and binary search strategy could be split into separate reference files for a cleaner overview, though for a skill of this size it's borderline acceptable.	2 / 3
	Total	10 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: quickwit-oss/tantivy
Commit: 46b3fb9

Reviewed: 7 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.