Status: Production Ready
Works with
Last Updated: 2026-02-03
Scope: npm, pnpm, yarn projects
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiondependency-auditExecute the skills CLI command in your project's root directory to begin installation:
Fetches dependency-audit from jezweb/claude-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate dependency-audit. Access via /dependency-audit in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
4
total installs
4
this week
697
GitHub stars
0
upvotes
Run in your terminal
4
installs
4
this week
697
stars
Status: Production Ready Last Updated: 2026-02-03 Scope: npm, pnpm, yarn projects
| Command | Purpose |
|---|---|
/audit-deps |
Run comprehensive dependency audit with prioritised findings |
/audit-deps # Full audit
/audit-deps --security-only # Only security vulnerabilities
/audit-deps --outdated # Only outdated packages
/audit-deps --fix # Auto-fix compatible updates
npm audit / pnpm audit
npm outdated / pnpm outdated
Categories:
Checks for:
═══════════════════════════════════════════════
DEPENDENCY AUDIT REPORT
═══════════════════════════════════════════════
Project: my-app
Package Manager: pnpm
Total Dependencies: 847 (142 direct, 705 transitive)
───────────────────────────────────────────────
SECURITY
───────────────────────────────────────────────
🔴 CRITICAL (1)
[email protected]
└─ CVE-2021-23337: Command injection via template()
└─ Fix: npm update [email protected]
└─ Affects: direct dependency
🟠 HIGH (2)
[email protected]
└─ CVE-2021-44906: Prototype pollution
└─ Fix: Transitive via mkdirp, update parent
└─ Path: mkdirp → minimist
[email protected]
└─ CVE-2022-0235: Exposure of sensitive headers
└─ Fix: npm update [email protected]
🟡 MODERATE (3)
[details...]
───────────────────────────────────────────────
OUTDATED PACKAGES
───────────────────────────────────────────────
Major Updates (review breaking changes):
react 18.2.0 → 19.1.0 (1 major)
typescript 5.3.0 → 5.8.0 (5 minor)
drizzle-orm 0.44.0 → 0.50.0 (6 minor)
Minor Updates (safe, new features):
@types/node 20.11.0 → 20.14.0
vitest 1.2.0 → 1.6.0
Patch Updates (recommended):
[15 packages with patch updates]
───────────────────────────────────────────────
LICENSE CHECK
───────────────────────────────────────────────
✅ All licenses compatible with MIT
Note: 3 packages use ISC (compatible)
───────────────────────────────────────────────
SUMMARY
───────────────────────────────────────────────
Security Issues: 6 (1 critical, 2 high, 3 moderate)
Outdated: 23 (3 major, 5 minor, 15 patch)
License Issues: 0
Recommended Actions:
1. Fix critical: npm update lodash
2. Fix high: npm audit fix
3. Review major updates before upgrading
═══════════════════════════════════════════════
The dep-auditor agent can:
- name: Audit dependencies
run: npm audit --audit-level=high
continue-on-error: true
- name: Check for critical vulnerabilities
run: |
CRITICAL=$(npm audit --json | jq '.metadata.vulnerabilities.critical')
if [ "$CRITICAL" -gt 0 ]; then
echo "Critical vulnerabilities found!"
exit 1
fi
#!/bin/sh
npm audit --audit-level=critical || {
echo "Critical vulnerabilities found. Run 'npm audit fix' or '/audit-deps'"
exit 1
}
| Task | npm | pnpm | yarn |
|---|---|---|---|
| Audit | npm audit |
pnpm audit |
yarn audit |
| Audit JSON | npm audit --json |
pnpm audit --json |
yarn audit --json |
| Fix auto | npm audit fix |
pnpm audit --fix |
yarn audit --fix |
| Fix force | npm audit fix --force |
N/A | N/A |
| Outdated | npm outdated |
pnpm outdated |
yarn outdated |
| Why | npm explain <pkg> |
pnpm why <pkg> |
yarn why <pkg> |
Version: 1.0.0 Last Updated: 2026-02-03
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
jezweb/claude-skills
shadcn/improve
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
We added dependency-audit from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
dependency-audit reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: dependency-audit is focused, and the summary matches what you get after install.
dependency-audit is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend dependency-audit for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in dependency-audit — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
dependency-audit has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: dependency-audit is the kind of skill you can hand to a new teammate without a long onboarding doc.
Keeps context tight: dependency-audit is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for dependency-audit matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 40