cve-risk-score — Claude Code skill: CVE lookup and install
The cve-risk-score skill looks up CVE records in NVD and reports CVSS score, severity, CWE, and description. It runs when a CVE ID appears in the conversation.
MIT 185 installs ★ 632 updated 2026-07-29
npx skills add transilienceai/communitytools --skill cve-risk-score -a claude-codeWhat cve-risk-score does
When a CVE ID appears in a message or scan output, the skill passes it to tools/nvd-lookup.py for an NVD lookup. Results appear inline for a single vulnerability or in a Markdown table for several. The agent then returns to the original task, using the lookup as supporting context.
The script requires Python 3. Set NVD_API_KEY in .env for the script to use the key and access higher request limits; unauthenticated bulk requests may be throttled by NVD. The skill reports NVD’s returned data rather than estimating a score. If NVD cannot be reached or has not scored a CVE, the result reflects that.
What it helps with
- look up a CVSS score for a mentioned CVE
- show a vulnerability’s severity and CWE
- compare several CVE records in a table
- add NVD context to code-scanning findings
Example prompts for the agent
- Look up
CVE-2024-12345in NVD and report its score, severity, and CWE. - Put the NVD results for these CVEs in a table, then continue reviewing the findings.
- Add the NVD description and risk score for the CVE found in this scan.
How to install cve-risk-score
1Skills CLI (Vercel)
npx skills add transilienceai/communitytools --skill cve-risk-score -a claude-code2Manually: put the files in place
~/.claude/skills/cve-risk-score/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/cve-risk-score/
1Skills CLI (Vercel)
npx skills add transilienceai/communitytools --skill cve-risk-score -a codex2Manually: put the files in place
.agents/skills/cve-risk-score/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add transilienceai/communitytools --skill cve-risk-score -a cursor2Manually: put the files in place
.cursor/skills/cve-risk-score/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install transilienceai/communitytools skills/cve-risk-score2Manually: put the files in place
.github/skills/cve-risk-score/SKILL.md1Skills CLI (Vercel)
npx skills add transilienceai/communitytools --skill cve-risk-score -a gemini-cli2Platform CLI
gemini skills install https://github.com/transilienceai/communitytools --path skills/cve-risk-scoreManually: put the files in place
.devin/skills/cve-risk-score/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add transilienceai/communitytools --skill cve-risk-score -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about cve-risk-score
How do I install cve-risk-score in Claude Code?
Run npx skills add transilienceai/communitytools --skill cve-risk-score -a claude-code. The skill file is at ~/.claude/skills/cve-risk-score/SKILL.md.
What does cve-risk-score do?
It looks up CVE IDs in NVD and displays their CVSS score, severity, CWE, and description. Multiple results are presented in a table.
Do I need an API key to look up CVEs?
No key is required. If NVD_API_KEY is set in .env, the script uses it for higher request limits; NVD may throttle bulk requests without a key.
Source text
SKILL.md · MIT
---
name: cve-risk-score
description: Retrieve CVE risk scores from NVD. Auto-invoked whenever a CVE ID is mentioned to display CVSS score, severity, CWE, and description.
---
# CVE Risk Score
Fetch and display CVE risk scores from the National Vulnerability Database (NVD) whenever a CVE ID appears in conversation.
## Trigger
This skill MUST be invoked automatically whenever a CVE ID (pattern `CVE-YYYY-NNNNN`) is mentioned by the user or discovered during research/scanning. Do not wait for explicit invocation.
## Workflow
1. **Extract CVE IDs** from the user's message or tool output (regex: `CVE-\d{4}-\d{4,}`)
2. **Run the lookup script**:
```bash
python3 tools/nvd-lookup.py CVE-XXXX-XXXXX [CVE-YYYY-YYYYY ...]
```
3. **Present the results** in a concise table format:
| CVE ID | Score | Severity | CWE | Description |
|--------|-------|----------|-----|-------------|
| CVE-XXXX-XXXXX | 9.8 | CRITICAL | CWE-79 | ... |
4. **Continue with the user's original task** — the score lookup is supplementary context, not a blocking step.
## Output Format
When presenting CVE risk scores inline, use this compact format:
```
CVE-2024-12345: 9.8 CRITICAL (CWE-79) — Remote code execution via ...
```
For multiple CVEs, use a markdown table.
## Rules
1. **Always invoke** — every CVE ID mentioned triggers a lookup. No exceptions.
2. **Non-blocking** — fetch scores in parallel with other work when possible.
3. **Accurate data only** — display exactly what NVD returns. Never estimate or fabricate scores.
4. **Graceful degradation** — if NVD is unreachable or the CVE has no score yet, say so explicitly (e.g., "Not yet scored by NVD").
5. **Rate limiting** — the script handles rate limits internally. For bulk lookups (5+), warn that NVD throttles unauthenticated requests.
6. **API key** — if `NVD_API_KEY` is set in `.env`, the script uses it for higher rate limits.
## Integration
This skill complements other skills:
- **cve-poc-generator**: After seeing the risk score, the user may want a full PoC and report
- **reconnaissance / source-code-scanning**: When these skills discover CVEs in dependencies, auto-lookup their scores
- **coordination**: CVE scores inform priority and severity classification in findings
© transilienceai · MIT · transilienceai/communitytools