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.
Install
git clone https://github.com/mvanhorn/cli-printing-press /tmp/cli-printing-press && ln -s /tmp/cli-printing-press/skills/printing-press ~/.claude/skills/printing-pressFrom README
/printing-press Result: A working Go CLI in $PRESSLIBRARY/ /, plus up to five dense manuscripts archived to $PRESSMANUSCRIPTS/ / /: 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.
More from this repo
printing-press-amend
Amend a published CLI from one of two input sources: (1) dogfood mode mines the active Claude Code session transcript...
printing-press-import
Bring a published CLI from the public library into the internal library so it's identical to a freshly-generated copy —...
printing-press-output-review
Internal sub-skill: agentic review of a printed CLI's sampled command output for plausibility issues that rule-based...