Analyze Cargo.toml dependencies and attempt to remove unused features to reduce compile times and binary size
74
72%
Does it follow best practices?
Impact
62%
1.40xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/rationalize-deps/SKILL.mdDependency feature rationalization workflow
serde default-features disabled
0%
100%
tokio default-features disabled
0%
100%
serde derive feature kept
100%
100%
tokio macros feature kept
100%
100%
tokio rt feature kept
100%
100%
cargo check command documented
0%
0%
cargo tree command used
0%
0%
cargo metadata command used
0%
0%
original config documented
100%
100%
new config documented
100%
100%
features removed documented
25%
62%
required features documented
100%
100%
Binary search for minimal feature set
reqwest default-features disabled
100%
100%
cargo metadata used
0%
0%
binary search methodology
0%
0%
iterative compilation checks
0%
0%
default features listed
75%
75%
rustls-tls or tls feature selected
100%
100%
json feature selected
100%
100%
unnecessary features removed
100%
100%
feature justifications provided
87%
100%
final verification commands
0%
25%
features removed listed
80%
80%
Workspace-wide analysis, prioritization, and full build verification
serde rationalized in core
0%
100%
tokio rationalized in core
100%
100%
tokio rationalized in cli
42%
100%
clap rationalized
33%
100%
serde rationalized in utils
0%
100%
cargo tree -d for duplicates
0%
22%
prioritization rationale
25%
37%
dev-dependencies consideration
77%
100%
final cargo check --all-targets
0%
0%
cargo test --no-run
0%
0%
per-dependency docs
88%
100%
cargo tree features command
0%
0%
cargo metadata command
0%
0%
cfb53e9
Table of Contents
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.