Skill security vulnerability management
Security vulnerability skill — CVE search, dependency audit, risk scoring, remediation plans
npx -y skills add zavora-ai/skill-security-vulnerability-managementAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Manage security vulnerabilities — search advisories (CVE/GHSA/OSV/RustSec), audit dependencies, score risk, generate remediation plans, and export findings. Use when checking for vulnerabilities, auditing dependencies, assessing security risk, planning patches, or generating security reports.
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.1 KB, 342 tokens by cl100k_base, as published. Nobody here has run it
Security Vulnerability Management
You manage security vulnerabilities. Search advisories, audit dependencies, score risk, and generate remediation plans. Critical/exploitable vulnerabilities are P0 — immediate action.
Decision Tree
├── "vulnerability", "CVE", "advisory"? → search_advisories / get_advisory
├── "audit", "scan", "dependencies"? → audit_dependencies
├── "risk", "score", "severity"? → score_risk
├── "fix", "patch", "remediate"? → remediation_plan
├── "report", "export", "evidence"? → export_findings
Key Workflows
Dependency Audit (3 calls)
audit_dependencies(manifest: "Cargo.lock")→ find vulnerable depsscore_risk(findings)→ prioritize by exploitability + exposureremediation_plan(findings)→ upgrade paths with breaking change warnings
CVE Investigation (2 calls)
search_advisories(query: "CVE-2025-XXXX")→ advisory detailsscore_risk(advisory, context: "our_usage")→ is it reachable in our code?
MUST DO
- Treat critical/exploitable as P0 (immediate action)
- Verify patches actually resolve the vulnerability
- Export evidence for all remediation actions
- Re-scan after patching
MUST NOT DO
- Never suppress advisories without documented risk acceptance
- Don't just bump versions — verify the fix
- Don't delay critical patches for convenience
What ships with it: 8 files
6.8 KB alongside SKILL.md, 1 of them executable
assets/
references/
- cross-mcp-workflows.md1.1 KB
- examples.md125 B
- tool-sequences.md131 B
scripts/
- prioritize_cves.pyruns912 B
- .gitignore29 B
- LICENSE738 B
- README.md3.1 KB