unclecheng-li/vulnclaw/cve-triage

Claude Code and agent skill by unclecheng-li/vulnclaw

Trust tier 2
  • community
LLM review pending
Source check pending

Checking that the SKILL.md file is still in the repository.

CVE lookup and triage — map discovered services/versions to known CVEs via the cve_lookup tool, score by CVSS/exploitability, and prioritize what to verify first.

Install

npx vskill@latest install unclecheng-li/vulnclaw/cve-triage

SKILL.md

The same SKILL.md was published earlier as unclecheng-li/vulnclaw/cve-triage.

CVE Triage

Turn version/banner evidence from recon into a prioritized, exploitability-aware list of CVEs worth verifying. Use this after fingerprinting a service, when a banner or Server: header reveals a product and version, or whenever the target exposes software with a known version.

The cve_lookup tool

VulnClaw ships a read-only cve_lookup tool backed by NVD:

  • Keyword search — cve_lookup(query="Apache httpd 2.4.49", limit=5) returns

the top CVEs sorted by CVSS, highest first.

  • CVE-ID detail — cve_lookup(query="CVE-2021-44228") returns the full record

plus best-effort exploit / PoC repositories discovered on GitHub.

It performs no egress to the target and is safe during recon. Without an NVD_API_KEY it still works (lower rate limit); set one for heavier use.

Workflow

  1. Extract product + version from recon — service banners, Server headers,

JS bundles, login footers, package manifests. A precise version string (OpenSSH 8.2p1, nginx 1.18.0) yields far better matches than a bare name.

  1. Query cve_lookup with "<product> <version>". Pull the detail record for

any high/critical hit by re-querying its CVE-ID.

  1. Score & prioritize — see references/cve-triage-workflow.md. Rank by CVSS,

then by exploit availability, then by exposure (is the vulnerable surface actually reachable on this target?).

  1. Confirm version applicability — match the target's version against the

CVE's affected cpe range before claiming it. Banner ≠ proof of vulnerability.

  1. Record findings with the CVE-ID, CVSS, and the evidence that maps this

target to it. Mark unconfirmed version-only matches as needs-manual-review, not verified.

Pitfalls

  • A keyword match is a hypothesis, not a finding — version ranges and backported

patches mean a banner version can be patched in place.

  • GitHub "PoC" repos are unverified third-party code; treat as leads, never run

blindly against a target.

  • Prefer the CVSS base score for triage, but let exploit availability and real

exposure override raw score when prioritizing verification effort.

Security

  • Security scanPassed, 100 of 100Pattern checks on the skill's files.
  • Model reviewNot runA model review is scheduled for the next rescan.

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
2,920
Repository forks
394
7-day trend score
40

Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/unclecheng-li/vulnclaw/cve-triage/badge)](https://verified-skill.com/skills/unclecheng-li/vulnclaw/cve-triage)

Something wrong with this skill or its page? Tell us.