mvanhorn/cli-printing-press
10 skills18.6k installs30.8k starsGitHub
Install
npx skills add https://github.com/mvanhorn/cli-printing-pressSkills in this repo
1Printing PressPrinting Press is an agent skill for solo and indie builders who need a useful command-line client around a real HTTP API without spending an hour on ceremonial phases. You point it at a product name (Notion, Discord), an OpenAPI file, a HAR export, or a Postman collection URL, and it runs a v2 lean loop: resolve the spec, write one research brief, generate the CLI skeleton, implement the highest-value gaps, then execute one consolidated shipcheck before optional live smoke tests against the API. Default mode keeps research, orchestration, implementation, and verification inside your primary agent; Codex mode pushes rote code-writing to Codex CLI when you flag it. The skill explicitly rejects the older pattern of many mandatory research documents upfront and many late validation passes that surface obvious failures too late. It is a workflow package for API CLIs—not a hosted MCP server—and pairs well with OpenAPI-first backends and agent-driven shipping habits.2.1kinstalls2Printing Press PolishPrinting Press Polish is a gate-focused playbook for solo builders shipping CLI content with mvanhorn’s cli-printing-press toolchain. When promote or publish refuses because the PII ledger still has pending hits, this skill walks you through auditing the CLI directory, replacing real customer PII with placeholders, or accepting justified false positives with a strict category and quoted evidence_context. Phase-one detection is intentionally shape-only—transaction identifiers, card last four, email, US phone, ZIP+4, and postal-address patterns—so passing the gate is necessary but not sufficient for “PII-clean” in every future detector class. Manuscript runs add research artifacts under .manuscripts paths so staged trees match what publish will scan. The workflow is procedural compliance: audit, resolve, re-audit until headers show no pending findings.2kinstalls3Printing Press Publishprinting-press-publish is an agent skill for the Printing Press CLI toolchain that takes a locally generated CLI from your library and publishes it to mvanhorn/printing-press-library as a pull request. Solo and indie builders who maintain reusable CLIs install it when a generated tool is ready for upstream contribution—not while still iterating on generator output. The workflow resolves the target CLI by name, runs publishing setup and validation, and can honor a polish handoff via --from-polish without treating that flag as a second confirmation on an already explicit publish request. A hard safety rule stops runs that were auto-continued from printing-press-polish’s Publish Offer; those must be restarted in a fresh user message with /printing-press-publish. Optional flags accommodate environments where live authentication tests cannot run. It fits builders standardizing on Printing Press who want agent-assisted fork, branch push, and PR creation instead of manual GitHub steps.2kinstalls4Printing Press Catalogprinting-press-catalog is a deprecated Claude Code skill for browsing and installing pre-built Go command-line clients for popular APIs from the cli-printing-press catalog. Solo and indie builders who previously used `/printing-press-catalog`, `/printing-press-catalog install stripe`, or search-by-keyword flows should switch to `/printing-press <API>` for generation and install, or run `cli-printing-press catalog list` in the terminal when they only need to browse entries. The skill still documents prerequisites—Go 1.26.3 or newer and the v4 binary installed with `go install github.com/mvanhorn/cli-printing-press/v4/cmd/cli-printing-press@latest`—plus a setup contract that resolves repo scope, prefers a local `cli-printing-press` build when you are inside the printing-press repo, and enforces min-binary-version 4.0.0. It fits builders shipping CLI or API-backed tools who want repeatable, typed HTTP CLIs without hand-writing every client. Because it is explicitly deprecated, treat this page as migration guidance rather than the primary install path.2kinstalls5Printing Press Reprintprinting-press-reprint is for solo builders who already shipped a Printing Press CLI and want a clean regeneration under a newer machine instead of endless manual patches. You invoke it with a CLI name and optional rationale— for example when a new MCP intent surface makes the old endpoint-mirror CLI obsolete. The skill ensures the prior artifact is present locally (fetching from the public library if needed), evaluates whether stale research should be reused or redone, and packages prior novel features plus post-publish hand-fixes as reconciliation input rather than losing that history. It then delegates to `/printing-press` so the novel-features pass can decide what to keep, reframe, or drop with documented reasons. Allowed tools include Bash, Read, AskUserQuestion, and Skill invocation, which matches an orchestration workflow more than a one-shot code edit. Use when a machine upgrade clearly beats polishing the old tree in place.2kinstalls6Printing Press Output Reviewprinting-press-output-review is an internal checker in the Printing Press ecosystem that samples a printed CLI’s command output and judges plausibility issues automated dogfood, verify, and `scorecard --live-check` rules cannot encode. Solo builders shipping agent-invokable CLIs benefit indirectly: parents invoke it at shipcheck Phase 4.85 and during the polish diagnostic loop so ranking, formatting, and silent data-loss problems surface before publish. It is not user-invocable standalone—floating findings without a ship verdict or fix loop would be misleading. The forked context isolates diagnostic narration. Findings are warnings under Wave B policy, preserving ship flow while still flagging subjective quality risks. Use the actionable wrappers `/printing-press` and `/printing-press-polish` rather than calling this skill directly.1.9kinstalls7Printing Press ScorePrinting-press-score is a slash-command skill for the cli-printing-press toolchain that evaluates generated command-line interfaces against the Steinberger quality bar. Indie builders shipping Go CLIs use it to rescore the working tree, target a named build, or pit two implementations against each other before tagging a release. The flow starts with a setup contract that locates the cli-printing-press binary—preferring a local build when you are inside the printing-press repo—and then runs scoring commands appropriate to your invocation pattern. It pairs naturally with generators that emit CLIs from specs, giving you an objective checklist instead of subjective "feels fine" reviews. Intermediate complexity reflects Go tooling, PATH discipline, and optional comparison workflows rather than a single-button linter.1.9kinstalls8Printing Press Retroprinting-press-retro documents Phase 6 artifact packaging and upload for the CLI Printing Press retro workflow. The agent creates a temporary staging directory, copies the manuscript run directory wholesale, and when CLI_DIR is set mirrors CLI source with rsync exclusions so binaries, vendor trees, and VCS metadata never bloat the bundle. Upload is deliberately gated behind user confirmation so solo builders do not accidentally publish drafts. Failure handling and final cleanup are sequenced so a bad upload does not corrupt local manuscripts or library paths. The skill suits authors who already finished a run and need a safe, repeatable handoff to whatever submission endpoint the press expects.1.9kinstalls9Printing Press ImportPrinting Press import backup is a small bash workflow for developers who maintain internal API slugs inside the Printing Press home directory and need a safety net before destructive imports. The import-backup script accepts a single api-slug, stages library and manuscript folders into a temp directory, and emits a quiet zip whose path is printed on stdout for scripting. It respects PRINTING_PRESS_HOME when set and defaults to ~/printing-press, which matches how solo builders isolate per-API tooling. Use it when you are about to overwrite a library entry or sync from a remote subtree and cannot afford to lose local manuscripts. The skill is narrow by design: it is not a full migration framework but a reproducible backup gate. After running, you have an absolute zip path suitable for manual restore or CI artifacts.1.9kinstalls10Printing Press Amendprinting-press-amend is a reference-loaded parsing layer for the Printing Press amend workflow when users supply explicit asks in `/printing-press-amend` instead of session dogfood. Solo and indie builders who ship Claude Code CLI skills use it to convert verbatim prompt text into a structured finding list Phase 2 can act on, without re-reading the full conversation history. It applies when MODE=direct is detected in Phase 0 or when running direct input alongside dogfood in MODE=both. The rubric ties natural-language verbs to finding types so amendments stay consistent with the rest of the printing-press stack. It deliberately does not infer asks from older chat turns—that behavior stays in transcript-parsing for MODE=dogfood. Pair it with the parent printing-press skills when you already know what you want changed and want the agent to formalize those edits as findings.906installs