Agent skill · software engineering · mvanhorn
printing-press
Set up a new integration, connector, or CLI binding for any API. Wrap or generate a ship-ready Go CLI from an OpenAPI, HAR, or Postman spec via the lean research -> generate -> build -> shipcheck loop. Use when the user says build a CLI, wrap this API, set up a new integration, add a connector, integrate with a service, or names an API by domain.
Why this skill is useful
Adds a complete executable workflow for generating and validating Go CLIs from various API specifications, which the AI cannot generate on its own.
What it needs
Requires go installed locally. About 2k tokens when loaded. Last updated 2026-08-06. 4,383 stars on the source repository.
What this skill does
/printing-press Result: A working Go CLI in $PRESSLIBRARY/<api-slug>/, plus up to five dense manuscripts archived to $PRESSMANUSCRIPTS/<api-slug>/<run-id>/: research brief, absorb manifest, build log, shipcheck proof, and live smoke proof when live testing ran. Next consumer: The user, who runs the CLI or ships it, and the sibling skills that take it from here: printing-press-polish for a second pass, printing-press-publish for the public library, printing-press-retro for findings against the Press itself. Done: Every feature approved at the absorb gate is implemented, shipcheck reached ship, the live dogfood matrix ran against real targets, the CLI is promoted, and the receipt ledger closes on the last phase. Intent: The best useful CLI for an API without an hour of phase theater. Optimize for time-to-ship, not time-to-document: reuse prior research when it is already good enough, run the cheap high-signal checks early, fix blockers before polish. Boundaries Never leak a secret. API key values, token values, passwords, and session cookies must never reach source, manuscripts, proofs, READMEs, HARs, receipts, or anything committed. Env var names and placeholders are safe. Phase 5.6 and publish apply references/secret-protection.md. Never ship untested. go build and verify pass-rate are structural signals, not correctness signals. A CLI that has not been through the live matrix in phases/18-dogfood-testing.md is not shippable, and a bug a 1-3 file edit resolves is fixed now, not filed for v0.2. Never quote human-time estimates for sub-tasks ("~15-30 min", "quick fix"). The agent does the work, not the user; describe scope instead. The carve-outs are the genuinely time-bound: the whole run (30-60 minutes), tool installs, and the network-bound printing-press subcommands. Never sequence from memory. The receipt ledger decides which phase comes next; see references/phase-receipts.md. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills mvanhorn/printing-press