pp-nvd — Claude Code skill: vulnerability search
pp-nvd searches the National Vulnerability Database for CVEs by product, identifier, or keyword, with related CVSS scores. Useful when checking a dependency for known issues.
Apache-2.0 271 installs ★ 2,142 updated 2026-10-24
npx skills add mvanhorn/printing-press-library --skill pp-nvd -a claude-codeWhat pp-nvd does
The skill drives the nvd-pp-cli binary. It searches CVE records by keyword, CVE ID, CPE name, publication date, or CVSS severity. A separate command finds exact CPE names for products. Results can be returned as JSON, with --select to keep chosen fields.
Install the CLI before running the skill. Check it with nvd-pp-cli --version and make sure its directory is on $PATH. No authentication is required. Searches can use the API or a local SQLite store when one is available; the CLI is for reading data, not changing remote state.
The nvd-pp-cli binary is required, so skill commands will not run without it. A Go installation is another option and requires Go 1.26.6 or newer.
What it helps with
- find CVEs by product name
- check a CVE's CVSS score
- identify the exact CPE name for a product
- filter vulnerabilities by publication date
Example prompts for the agent
- Find product vulnerabilities with
nvd-pp-cli json search-cves. - Look up the matching CPE name using
nvd-pp-cli json search-cpes. - Check the CVSS details for this CVE with
nvd-pp-cli json search-cves.
How to install pp-nvd
1Skills CLI (Vercel)
npx skills add mvanhorn/printing-press-library --skill pp-nvd -a claude-code2Manually: put the files in place
~/.claude/skills/pp-nvd/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/pp-nvd/
1Skills CLI (Vercel)
npx skills add mvanhorn/printing-press-library --skill pp-nvd -a codex2Manually: put the files in place
.agents/skills/pp-nvd/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add mvanhorn/printing-press-library --skill pp-nvd -a cursor2Manually: put the files in place
.cursor/skills/pp-nvd/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install mvanhorn/printing-press-library cli-skills/pp-nvd/SKILL.md2Manually: put the files in place
.github/skills/pp-nvd/SKILL.md1Skills CLI (Vercel)
npx skills add mvanhorn/printing-press-library --skill pp-nvd -a gemini-cli2Platform CLI
gemini skills install https://github.com/mvanhorn/printing-press-library --path cli-skills/pp-nvdManually: put the files in place
.devin/skills/pp-nvd/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add mvanhorn/printing-press-library --skill pp-nvd -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 pp-nvd
How do I install pp-nvd in Claude Code?
Run npx skills add mvanhorn/printing-press-library --skill pp-nvd -a claude-code. The skill file will be at ~/.claude/skills/pp-nvd/SKILL.md.
What does pp-nvd do?
It uses nvd-pp-cli to search the National Vulnerability Database for CVE and CPE records. Searches can use a product, CVE ID, keyword, date, or CVSS severity.
Do I need an API key to search?
No authentication is required. The skill's CLI commands are read-only and are not for changing remote data.
Source text
SKILL.md · Apache-2.0
---
name: pp-nvd
description: "Search the U.S. National Vulnerability Database for CVEs, CVSS scores, affected versions, and severity ratings — by keyword, product (CPE name), CVE ID, or date range. Trigger phrases: `look up CVE`, `CVSS score for`, `vulnerabilities in <product>`, `use nvd`."
author: "Hiten Shah"
license: "Apache-2.0"
argument-hint: "<command> [args] | install cli|mcp"
allowed-tools: "Read Bash"
metadata:
openclaw:
requires:
bins:
- nvd-pp-cli
install:
- kind: go
bins: [nvd-pp-cli]
module: github.com/mvanhorn/printing-press-library/library/developer-tools/nvd/cmd/nvd-pp-cli
---
<!-- GENERATED FILE — DO NOT EDIT.
This file is a verbatim mirror of library/developer-tools/nvd/SKILL.md,
regenerated post-merge by tools/generate-skills/. Hand-edits here are
silently overwritten on the next regen. Edit the library/ source instead.
See the repository agent guide, section "Generated artifacts: registry.json, cli-skills/". -->
# Nvd — Printing Press CLI
## Prerequisites: Install the CLI
This skill drives the `nvd-pp-cli` binary. **You must verify the CLI is installed before invoking any command from this skill.** If it is missing, install it first:
1. Install via the Printing Press installer. It defaults binaries to `$HOME/.local/bin` on macOS/Linux and `%LOCALAPPDATA%\Programs\PrintingPress\bin` on Windows:
```bash
npx -y @mvanhorn/printing-press-library install nvd --cli-only
```
2. Verify: `nvd-pp-cli --version`
3. Ensure the reported install directory is on `$PATH` for the agent/runtime that will invoke this skill.
If the `npx` install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.6 or newer):
```bash
go install github.com/mvanhorn/printing-press-library/library/developer-tools/nvd/cmd/nvd-pp-cli@latest
```
If `--version` reports "command not found" after install, the runtime cannot see the binary directory on `$PATH`. Do not proceed with skill commands until verification succeeds.
## When Not to Use This CLI
Do not activate this CLI for requests that require creating, updating, deleting, publishing, commenting, upvoting, inviting, ordering, sending messages, booking, purchasing, or changing remote state. This printed CLI exposes read-only commands for inspection, export, sync, and analysis.
## Command Reference
**json** — Manage json
- `nvd-pp-cli json search-cpes` — Search Common Platform Enumeration names to find exact product identifiers for vulnerability lookups.
- `nvd-pp-cli json search-cves` — Search vulnerabilities by keyword, CVE ID, CPE name, publication date, or CVSS severity.
### Finding the right command
When you know what you want to do but not which command does it, ask the CLI directly:
```bash
nvd-pp-cli which "<capability in your own words>"
```
`which` resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code `0` means at least one match; exit code `2` means no confident match — fall back to `--help` or use a narrower query.
## Auth Setup
No authentication required.
Run `nvd-pp-cli doctor` to verify setup.
## Agent Mode
Add `--agent` to any command. Expands to: `--json --compact --no-input --no-color --yes`.
- **Pipeable** — JSON on stdout, errors on stderr
- **Filterable** — `--select` keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs:
```bash
nvd-pp-cli json search-cpes --agent --select id,name,status
```
- **Previewable** — `--dry-run` shows the request without sending
- **Offline-friendly** — sync/search commands can use the local SQLite store when available
- **Non-interactive** — never prompts, every input is a flag
- **Read-only** — do not use this CLI for create, update, delete, publish, comment, upvote, invite, order, send, or other mutating requests
### Response envelope
Commands that read from the local store or the API wrap output in a provenance envelope:
```json
{
"meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."},
"results": <data>
}
```
Parse `.results` for data and `.meta.source` to know whether it's live or local. A human-readable `N results (live)` summary is printed to stderr only when stdout is a terminal — piped/agent consumers get pure JSON on stdout.
## Agent Feedback
When you (or the agent) notice something off about this CLI, record it:
```
nvd-pp-cli feedback "the --since flag is inclusive but docs say exclusive"
nvd-pp-cli feedback --stdin < notes.txt
nvd-pp-cli feedback list --json --limit 10
```
Entries are stored locally at `~/.nvd-pp-cli/feedback.jsonl`. They are never POSTed unless `NVD_FEEDBACK_ENDPOINT` is set AND either `--send` is passed or `NVD_FEEDBACK_AUTO_SEND=true`. Default behavior is local-only.
Write what *surprised* you, not a bug report. Short, specific, one line: that is the part that compounds.
## Output Delivery
Every command accepts `--deliver <sink>`. The output goes to the named sink in addition to (or instead of) stdout, so agents can route command results without hand-piping. Three sinks are supported:
| Sink | Effect |
|------|--------|
| `stdout` | Default; write to stdout only |
| `file:<path>` | Atomically write output to `<path>` (tmp + rename) |
| `webhook:<url>` | POST the output body to the URL (`application/json` or `application/x-ndjson` when `--compact`) |
Unknown schemes are refused with a structured error naming the supported set. Webhook failures return non-zero and log the URL + HTTP status on stderr.
## Named Profiles
A profile is a saved set of flag values, reused across invocations. Use it when a scheduled agent calls the same command every run with the same configuration - HeyGen's "Beacon" pattern.
```
nvd-pp-cli profile save briefing --json
nvd-pp-cli --profile briefing json search-cpes
nvd-pp-cli profile list --json
nvd-pp-cli profile show briefing
nvd-pp-cli profile delete briefing --yes
```
Explicit flags always win over profile values; profile values win over defaults. `agent-context` lists all available profiles under `available_profiles` so introspecting agents discover them at runtime.
## Exit Codes
| Code | Meaning |
|------|---------|
| 0 | Success |
| 2 | Usage error (wrong arguments) |
| 3 | Resource not found |
| 5 | API error (upstream issue) |
| 7 | Rate limited (wait and retry) |
| 10 | Config error |
## Argument Parsing
Parse `$ARGUMENTS`:
1. **Empty, `help`, or `--help`** → show `nvd-pp-cli --help` output
2. **Starts with `install`** → ends with `mcp` → MCP installation; otherwise → see Prerequisites above
3. **Anything else** → Direct Use (execute as CLI command with `--agent`)
## MCP Server Installation
1. Install the MCP server:
```bash
go install github.com/mvanhorn/printing-press-library/library/developer-tools/nvd/cmd/nvd-pp-mcp@latest
```
2. Register with Claude Code:
```bash
claude mcp add nvd-pp-mcp -- nvd-pp-mcp
```
3. Verify: `claude mcp list`
## Direct Use
1. Check if installed: `which nvd-pp-cli`
If not found, offer to install (see Prerequisites at the top of this skill).
2. Match the user query to the best command from the Command Reference above, or resolve it with `nvd-pp-cli which "<capability>"`.
3. Execute with the `--agent` flag:
```bash
nvd-pp-cli <command> [subcommand] [args] --agent
```
4. If ambiguous, drill into subcommand help: `nvd-pp-cli <command> --help`.
© Hiten Shah · Apache-2.0 · mvanhorn/printing-press-library