Individual skill
dependency-auditor
Reviews package dependencies for unnecessary packages, outdated or risky patterns, duplication, and licensing/maintenance risk. Use when a dependency manifest has grown unchecked or before adding a new dependency.
skills/development/dependency-auditor/SKILL.md
Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 27
- Repository last updated
- Aug 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- ai Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- ai-skill Repository topic
- ai-skill-enhancement Repository topic
- ai-skills Repository topic
- ai-skills-analysis Repository topic
- ai-skills-fest Repository topic
- ai-skills-manager Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
README.mddoc · 1,239 bytesSKILL.mdcore · 2,633 bytesexamples/example.mddoc · 1,708 bytes
Read excerpt
## Purpose
Review a project's dependency manifest for bloat, risk, and duplication — packages that shouldn't be there, packages that duplicate functionality, and packages that carry maintenance or licensing risk.
## When to Use
- The dependency list has grown over time without anyone auditing it.
- Before adding a new dependency, to check if an existing one already covers the need.
- Investigating bundle size or install time bloat.
## What to Analyze
1. **Unnecessary packages** — dependencies for functionality that's a few lines of code, or that duplicate a built-in language/runtime feature.
2. **Duplication** — multiple packages solving the same problem (e.g. two date libraries, two HTTP clients) introduced at different times by different people.