Skip to main content
skill CX Codex

cve-poc-generator — Claude Code skill: what it does, how to install

The cve-poc-generator skill researches a CVE, writes a safe Python PoC, and produces a vulnerability report. Use it when you need sourced verification and remediation details.

MIT 236 installs ★ 632 updated 2026-07-29

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add transilienceai/communitytools --skill cve-poc-generator -a claude-code
Open on GitHub

What cve-poc-generator does

cve-poc-generator takes one CVE ID and pulls records from the NVD API v2.0. It also examines vendor advisories, GitHub Security Advisories, Exploit-DB, and published analyses. The workflow extracts the applicable CVSS score and vector, CWE IDs, affected product matches, advisory references, and patch links before documenting the root cause and attack path.

The generated files are poc.py under artifacts/cve-pocs/CVE-XXXX-XXXXX/ and report.md under reports/cve-pocs/CVE-XXXX-XXXXX/. The PoC is meant to run with Python’s standard library plus requests, without framework dependencies. Its default behavior is read-only and non-destructive; any risky operation needs an explicit --confirm flag. Reports attribute claims to sources, and CVSS values come from NVD rather than estimation.

What it helps with

  • research a CVE from its identifier
  • collect CVSS, CWE, and affected versions
  • write a standalone Python verification PoC
  • produce a sourced report with remediation guidance

Example prompts for the agent

  • Run /cve-poc-generator CVE-2024-XXXXX and create the PoC with its report.
  • Research /cve-poc-generator CVE-2024-XXXXX, check NVD references, and save the findings to report.md.
  • Process /cve-poc-generator CVE-2024-XXXXX using read-only checks and no destructive payloads.

How to install cve-poc-generator

1Skills CLI (Vercel)

npx skills add transilienceai/communitytools --skill cve-poc-generator -a claude-code

2Manually: put the files in place

~/.claude/skills/cve-poc-generator/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/cve-poc-generator/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about cve-poc-generator

How do I install cve-poc-generator in Claude Code?

Run npx skills add transilienceai/communitytools --skill cve-poc-generator -a claude-code, then use ~/.claude/skills/cve-poc-generator/SKILL.md.

What does cve-poc-generator do?

It researches a CVE through NVD and advisory sources, creates a standalone Python PoC, and writes a Markdown report covering the cause, risk, evidence, and remediation.

Can one run process multiple CVEs?

No. Each invocation accepts one CVE ID, so multiple CVEs require separate invocations.

Source text

SKILL.md · MIT
---
name: cve-poc-generator
description: CVE research, standalone PoC script and report generation. Given a CVE ID, researches NVD and advisories, generates a safe Python PoC, and writes a detailed vulnerability report.
---

# CVE PoC Generator

Research a CVE by ID, generate a standalone Python proof-of-concept script, and produce a detailed vulnerability report.

## Workflow

1. **NVD Lookup** - Query NVD API v2.0 for the CVE ID (`python3 tools/nvd-lookup.py <CVE>`). Extract the CVSS score/vector using the v4.0-primary ladder (v4.0 → v3.1 → v3.0 → v2.0; the tool's `JSON_SUMMARY` exposes `cvss_version` + `cvss_vector`), plus CWE IDs, CPE matches, advisory URLs, and patch links.
2. **Advisory Research** - Deep-dive vendor advisories, GitHub security advisories, Exploit-DB, and published write-ups. Identify root cause, affected versions, and attack vector details.
3. **PoC Generation** - Write a standalone Python script (`poc.py`) that demonstrates the vulnerability safely. Follow the script standards in `reference/poc-methodology.md`.
4. **Report Generation** - Write a comprehensive markdown report (`report.md`) with metadata, root cause analysis, risk assessment, and remediation guidance.

## NVD Data to Collect

| Field | Source | Usage |
|-------|--------|-------|
| CVE ID | NVD | Primary identifier |
| CVSS Score + Vector (v4.0 primary; v3.1/v3.0/v2.0 fallback) | NVD | Risk scoring |
| CWE ID(s) | NVD | Vulnerability classification |
| CPE Matches | NVD | Affected products and versions |
| Advisory URLs | NVD references | Research sources |
| Patch Links | NVD references / vendor | Remediation guidance |
| Description | NVD | Vulnerability summary |
| Published / Modified dates | NVD | Timeline |

## Output

```
{OUTPUT_DIR}/
  artifacts/cve-pocs/CVE-XXXX-XXXXX/
    poc.py              # Standalone Python PoC script
  reports/cve-pocs/CVE-XXXX-XXXXX/
    report.md           # Detailed vulnerability report
```

## Invocation

```
/cve-poc-generator CVE-2024-XXXXX
```

The skill accepts a single CVE ID as argument. Multiple CVEs should be processed with separate invocations.

## Rules

1. **Least harm** - PoC scripts MUST demonstrate vulnerability without causing damage. Use detection/verification checks, not destructive payloads.
2. **Standalone scripts** - PoC must run independently with only standard Python libraries plus `requests`. No framework dependencies.
3. **Accurate scoring** - Use the exact CVSS score and vector from NVD. Do not fabricate or estimate scores.
4. **Source attribution** - Every claim in the report must cite its source (NVD, vendor advisory, CVE description).
5. **No emoji** - Use text severity labels only (CRITICAL, HIGH, MEDIUM, LOW, INFORMATIONAL).
6. **Verified data only** - Do not hallucinate CVE details. If NVD data is unavailable, state it explicitly.
7. **Safe defaults** - PoC scripts must default to read-only, non-destructive operations. Any potentially harmful action requires explicit `--confirm` flag.

© transilienceai · MIT · transilienceai/communitytools

Similar skills

All skills for Security →
bluehammer-vulnerability-poc reason-machines bluehammer-vulnerability-poc is a Claude Code skill for building and running the BlueHammer C PoC and finding bugs; it also works in Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode. CX Codex +1 578installs poc-validator 0xSteph poc-validator — a Claude Code subagent that generates and runs safe Proof of Concept scripts, confirms real vulnerabilities, and filters out false positives before including findings in a pentest report. CX Codex ★ 2,482repo stars cve-mcp-server-security-intelligence reason-machines cve-mcp-server-security-intelligence — a skill that runs a local MCP server and hands the agent 27 tools for CVE work: CVSS and EPSS scores, CISA KEV status, exploit hunting and a composite risk score. CX Codex +1 229installs CVE Analyzer microsoft CVE Analyzer — a subagent for deep CVE analysis: checks if vulnerable code is reachable in the project and returns evidence-backed VEX status. CX Codex +1 ★ 1,627repo stars EchelonGraph CVE & Exposure echelongraph EchelonGraph CVE & Exposure is an MCP server for Claude Code that checks vulnerabilities across NVD, KEV, and EPSS and assesses network exposure using Shodan. It helps audit SBOM files and lockfile dependencies. CX Codex +1 ★ 25repo stars sbom-cyclonedx-and-cve-reachability-tooling W4L33Dx sbom-cyclonedx-and-cve-reachability-tooling is a Claude Code skill that builds CycloneDX/SPDX validators and vulnerability ranking pipelines. Activates when developing SCA and CVE triage tools. CX Codex +1 ★ 73repo stars

From the same set42

The whole set →
blockchain-security blockchain-security is a skill that checks Solidity contracts and blockchain CTF challenges for common EVM flaws, including storage, delegatecall, and access-control issues. CX Codex +1 875installs hackerone Parses HackerOne scope tables, runs parallel pentesting agents per asset, and formats verified reports after checking exploit PoCs. CX Codex +1 348installs osint osint — a skill for passive intelligence gathering across code repositories, developer accounts, and exposed secrets. Discovers company repositories, scans commit history for sensitive data, maps API endpoints and internal infrastructure. CX Codex +1 251installs reconnaissance Runs domain reconnaissance: subdomains, open ports, endpoints and APIs, then sorts the attack surface by risk. CX Codex +1 248installs social-engineering social-engineering is a Claude Code skill for planning authorized tests of human-factor security. It covers phishing, pretexting, voice-based attacks, and physical security checks. CX Codex +1 224installs api-security api-security is a Claude Code skill that tests REST, GraphQL, WebSocket, and Web-LLM interfaces for authorization flaws and injection bugs across large endpoint collections. CX Codex +1 220installs web-app-logic web-app-logic — a skill for finding vulnerabilities in web application logic that automated scanners miss: workflow bypass, race conditions, access control flaws, cache poisoning, and information disclosure. CX Codex +1 219installs source-code-scanning source-code-scanning guides automated SAST, CVE scanning across project dependencies, and secrets detection to locate vulnerabilities before deployment. CX Codex +1 217installs

Project sponsors

Companies that keep this analytics open