Individual skill
dependency-vulnerability-triage
Triages CVEs and Dependabot/Snyk security alerts to assess real runtime exploitability and reduce alarm fatigue.
skills/security/dependency-vulnerability-triage/SKILL.md
Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- 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
- security 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 · 577 bytesSKILL.mdcore · 1,836 bytesexamples/example.mddoc · 782 bytes
Read excerpt
## Purpose
Triage and evaluate automated security alerts (Dependabot, Snyk, GitHub Advisory, Trivy) to determine true exploitability in your specific application context, distinguishing genuine high-risk threats from harmless dev-dependency false positives.
## When to Use
- Reviewing a barrage of automated Dependabot or Snyk PRs.
- Preparing for security compliance reviews where open CVEs must be justified or remediated.
- Deciding whether a vulnerability requires an emergency out-of-band deployment.
## What to Analyze
1. **Vulnerability Mechanics**: What exact function or API triggers the vulnerability (e.g. Prototype Pollution in `lodash.merge`, ReDoS in regex parser)?
2. **Reachable Attack Surface**: Does your application actually import and call the vulnerable function with untrusted user input?