Dependency Audit
SkillDev toolsAudit every crate's Cargo.toml for unused, duplicate or misplaced dependencies, moving shared deps to the workspace and feature-gating where sensible. Use when asked to audit or slim dependencies.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Dependency Audit skill
What this skill tells your AI
The instructions your AI receives, as published by mrchantey/beet in .agents/skills/test-dependency-audit/SKILL.md and read by ahel’s review.
perform a dependency audit on each crates Cargo.toml.
- ie
beet_netshould have very few required dependencies. http is one of many transports and should not be a hard requirement. - remove unused/duplicate deps.
- dependencies that are shared amongst crates belong in the workspace Cargo.toml
- dependencies that are used by only one crate belong in that crates Cargo.toml
- if a dep would be a better fit in an upstream or downstream crate in the workspace, move it over.
- feature gate where possible, but avoid feature spaghettification
Verification
- verify individual crates after making changes, including with/without the changed features.
- aggressively use tail for all tests to preserve context
Signals
- GitHub stars
- 134
- Forks
- 8
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
test-dependency-audit- Source
- github.com/mrchantey/beet