pp-openfda
Original:🇺🇸 English
Translated
Printing Press CLI for Openfda. The FDA safety data terminal. Every drug adverse event, device recall, food contamination, and product label the FDA...
15installs
Added on
NPX Install
npx skill4agent add mvanhorn/printing-press-library pp-openfdaTags
Translated version includes tags in frontmatterSKILL.md Content
View Translation Comparison →<!-- GENERATED FILE — DO NOT EDIT.
This file is a verbatim mirror of library/developer-tools/openfda/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 AGENTS.md "Generated artifacts: registry.json, cli-skills/". -->
resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code means at least one match; exit code means no confident match — fall back to or use a narrower query.
Openfda — Printing Press CLI
Prerequisites: Install the CLI
This skill drives the binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:
openfda-pp-cli- Install via the Printing Press installer:
bash
npx -y @mvanhorn/printing-press-library install openfda --cli-only - Verify:
openfda-pp-cli --version - Ensure (or
$GOPATH/bin) is on$HOME/go/bin.$PATH
If the install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.3 or newer):
npxbash
go install github.com/mvanhorn/printing-press-library/library/developer-tools/openfda/cmd/openfda-pp-cli@latestIf reports "command not found" after install, the install step did not put the binary on . Do not proceed with skill commands until verification succeeds.
--version$PATHWhen 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
animal-events — Animal drug and device adverse event reports.
- — Search animal adverse event reports
openfda-pp-cli animal-events
device-510k — Premarket notification submissions demonstrating substantial equivalence.
- — Search 510(k) clearance records
openfda-pp-cli device-510k
device-classification — Medical device product codes, specialty areas, and regulatory class.
- — Search device classifications
openfda-pp-cli device-classification
device-covid19 — COVID-19 serological testing evaluation data.
- — Search COVID-19 serology test evaluations
openfda-pp-cli device-covid19
device-events — Medical device adverse event reports (MAUDE/MDR) — injuries, deaths, malfunctions.
- — Count device events by field
openfda-pp-cli device-events count - — Search device adverse event reports
openfda-pp-cli device-events list
device-pma — Class III medical device premarket approval decisions.
- — Search premarket approval records
openfda-pp-cli device-pma
device-recall-detail — Detailed device recall actions addressing defects or health risks.
- — Search device recall action details
openfda-pp-cli device-recall-detail
device-recalls — Medical device recall enforcement reports.
- — Search device recall enforcement reports
openfda-pp-cli device-recalls
device-registration — Medical device manufacturing establishment registrations and product listings.
- — Search device registrations and listings
openfda-pp-cli device-registration
device-udi — Global Unique Device Identification Database (GUDID).
- — Search unique device identifiers
openfda-pp-cli device-udi
drug-approvals — FDA-approved drug products since 1939 — applications, submissions, and marketing status.
- — Search approved drug products
openfda-pp-cli drug-approvals
drug-events — Reports of drug side effects, medication errors, product quality problems (FAERS). 4.9M+ reports since 2003.
- — Count adverse events by field
openfda-pp-cli drug-events count - — Search drug adverse event reports
openfda-pp-cli drug-events list
drug-labels — Structured product information including prescribing info, black box warnings, indications.
- — Search drug product labels
openfda-pp-cli drug-labels
drug-ndc — National Drug Code directory — product identifiers, packaging, and classification.
- — Search NDC directory
openfda-pp-cli drug-ndc
drug-recalls — Drug product recall enforcement reports.
- — Count drug recalls by field
openfda-pp-cli drug-recalls count - — Search drug recall enforcement reports
openfda-pp-cli drug-recalls list
drug-shortages — Current and historical drug shortages from manufacturing issues, delays, and discontinuations.
- — Search drug shortages
openfda-pp-cli drug-shortages
food-events — CAERS reports — food, dietary supplement, and cosmetic adverse events.
- — Search food/supplement adverse event reports
openfda-pp-cli food-events
food-recalls — Food product recall enforcement reports.
- — Count food recalls by field
openfda-pp-cli food-recalls count - — Search food recall enforcement reports
openfda-pp-cli food-recalls list
nsde — Non-Standardized Drug Entities — drug names that don't map to standard terminology.
- — Search non-standardized drug entities
openfda-pp-cli nsde
substance — Substance data from the FDA substance registration system.
- — Search substance records
openfda-pp-cli substance
tobacco-problems — Tobacco product problem reports.
- — Search tobacco problem reports
openfda-pp-cli tobacco-problems
Finding the right command
When you know what you want to do but not which command does it, ask the CLI directly:
bash
openfda-pp-cli which "<capability in your own words>"which02--helpAuth Setup
Set your API key via environment variable:
bash
export FDA_API_KEY="<your-key>"Or persist it in ``.
Run to verify setup.
openfda-pp-cli doctorAgent Mode
Add to any command. Expands to: .
--agent--json --compact --no-input --no-color --yes-
Pipeable — JSON on stdout, errors on stderr
-
Filterable —keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs:
--selectbashopenfda-pp-cli animal-events --agent --select id,name,status -
Previewable —shows the request without sending
--dry-run -
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 for data and to know whether it's live or local. A human-readable summary is printed to stderr only when stdout is a terminal — piped/agent consumers get pure JSON on stdout.
.results.meta.sourceN results (live)Agent Feedback
When you (or the agent) notice something off about this CLI, record it:
openfda-pp-cli feedback "the --since flag is inclusive but docs say exclusive"
openfda-pp-cli feedback --stdin < notes.txt
openfda-pp-cli feedback list --json --limit 10Entries are stored locally at . They are never POSTed unless is set AND either is passed or . Default behavior is local-only.
~/.openfda-pp-cli/feedback.jsonlOPENFDA_FEEDBACK_ENDPOINT--sendOPENFDA_FEEDBACK_AUTO_SEND=trueWrite what surprised you, not a bug report. Short, specific, one line: that is the part that compounds.
Output Delivery
Every command accepts . 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:
--deliver <sink>| Sink | Effect |
|---|---|
| Default; write to stdout only |
| Atomically write output to |
| POST the output body to the URL ( |
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.
openfda-pp-cli profile save briefing --json
openfda-pp-cli --profile briefing animal-events
openfda-pp-cli profile list --json
openfda-pp-cli profile show briefing
openfda-pp-cli profile delete briefing --yesExplicit flags always win over profile values; profile values win over defaults. lists all available profiles under so introspecting agents discover them at runtime.
agent-contextavailable_profilesExit Codes
| Code | Meaning |
|---|---|
| 0 | Success |
| 2 | Usage error (wrong arguments) |
| 3 | Resource not found |
| 4 | Authentication required |
| 5 | API error (upstream issue) |
| 7 | Rate limited (wait and retry) |
| 10 | Config error |
Argument Parsing
Parse :
$ARGUMENTS- Empty, , or
help→ show--helpoutputopenfda-pp-cli --help - Starts with → ends with
install→ MCP installation; otherwise → see Prerequisites abovemcp - Anything else → Direct Use (execute as CLI command with )
--agent
MCP Server Installation
Install the MCP binary from this CLI's published public-library entry or pre-built release, then register it:
bash
claude mcp add openfda-pp-mcp -- openfda-pp-mcpVerify:
claude mcp listDirect Use
- Check if installed: If not found, offer to install (see Prerequisites at the top of this skill).
which openfda-pp-cli - Match the user query to the best command from the Unique Capabilities and Command Reference above.
- Execute with the flag:
--agentbashopenfda-pp-cli <command> [subcommand] [args] --agent - If ambiguous, drill into subcommand help: .
openfda-pp-cli <command> --help