Printing Press
Set up a new integration, connector, or CLI binding for any API.
Install
npx skills add mvanhorn/cli-printing-press --skill printing-press -g -a claude-code -y- Repository
- mvanhorn/cli-printing-press4.9k
- Category
- Writing
- Updated
- 3d ago
- License
- MIT
- Context cost
- Lightabout 1,244 tokens
- Runs scripts
- Yes, review before use
What it does
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.
/printing-press
Result: A working Go CLI in $PRESS_LIBRARY/<api-slug>/, plus up to five dense
manuscripts archived to $PRESS_MANUSCRIPTS/<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.
