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.
- Installs
- 7.6K
- Last 24h
- +23
- Trending rank
- #5161
- Security
- Warn
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/mvanhorn/cli-printing-press --skill printing-press- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads printing-press automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
Security audits
Independent scans of the skill's instructions and bundled files.
SKILL.md
The instructions your agent reads when the skill is triggered.
/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.
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 buildandverifypass-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.
Authority
Invocation authorizes reading and writing under $PRESS_RUNSTATE/, $PRESS_LIBRARY/,
and $PRESS_MANUSCRIPTS/, running the printing-press binary and the Go toolchain, and
researching the API on the open web. It does not authorize publishing to the public
library, opening a pull request, or writing anywhere else on the user's machine.
Steps
Enter phases/01-preflight.md before any user-facing prompt, then read references/run-resolution.md: it resolves the API target, the briefing context, and the source priority for combo runs.
Never execute a phase from memory. When you enter a phase, Read its file from phases/ first.
Code orchestration in phases/10-generate.md serves reads on <api>_read and previews state-changing <api>_execute calls until confirm is boolean true.
| Step | File |
|---|---|
| 1 | phases/01-preflight.md |
| 2 | phases/02-run-initialization.md |
| 3 | phases/03-resolve-and-reuse.md |
| 4 | phases/04-research-brief.md |
| 5 | phases/05-pre-browser-sniff-auth-intelligence.md |
| 6 | phases/06-browser-sniff-gate.md |
| 7 | phases/07-crowd-sniff-gate.md |
| 8 | phases/08-ecosystem-absorb-gate.md |
| 9 | phases/09-api-reachability-gate.md |
| 10 | phases/10-generate.md |
| 11 | phases/11-build-the-goat.md |
| 12 | phases/12-shipcheck.md |
| 13 | phases/13-sync-param-drop-gate.md |
| 14 | phases/14-agentic-skill-review.md |
| 15 | phases/15-readme-skill-agents-correctness-audit.md |
| 16 | phases/16-agentic-output-review.md |
| 17 | phases/17-local-code-review.md |
| 18 | phases/18-dogfood-testing.md |
| 19 | phases/19-polish.md |
| 20 | phases/20-promote-and-archive.md |
| 21 | phases/21-next-steps.md |
Follow each file's final Next: pointer, and record the receipt handoff each phase
names. Late procedure lives in the phase file or a role-named reference it loads
(references/phase-receipts.md, references/codex-delegation.md,
references/fetch-docs.md). Do not restate those files here.
FAQ
What does the printing-press skill do?
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.
How do I install printing-press?
Run npx skills add https://github.com/mvanhorn/cli-printing-press --skill printing-press in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/printing-press/ (personal) or .claude/skills/printing-press/ (project).
Which AI agents can use printing-press?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is printing-press safe to install?
Security partners have reviewed it: Gen Agent Trust Hub passed; Socket flagged items to review; Snyk flagged items to review. As with any skill, read the SKILL.md and bundled scripts before installing.
Who maintains printing-press?
It is published by mvanhorn in mvanhorn/cli-printing-press. It has 7,618 recorded installs.
More from mvanhorn/cli-printing-press
printing-press-publish
mvanhorn/cli-printing-press
Publish a generated CLI to the printing-press-library repo
printing-press-polish
mvanhorn/cli-printing-press
Polish a generated CLI to pass verification and become publish-ready. Runs diagnostics (dogfood, verify, scorecard, go vet, gosec), automatically fixes all issues (verify failures, static-analysis findings, dead code, descriptions, README, MCP tool quality), reports the before/after delta, and offers to publish. Use after any /printing-press run, or on any CLI in $PRESSLIBRARY/. Trigger phrases: "polish", "improve the CLI", "fix verify", "make it publish-ready", "clean up the CLI", "get this ready to ship".
printing-press-import
mvanhorn/cli-printing-press
Bring a published CLI from the public library into the internal library so it's identical to a freshly-generated copy — module path reverted, manuscripts placed alongside, ready for /printing-press-polish or /printing-press-emboss. Use when the public library has a CLI you don't have locally, or to recover from a broken/lost internal copy. Trigger phrases: "import the CLI", "bring it into my library", "fetch from public library", "I don't have it locally yet".
printing-press-retro
mvanhorn/cli-printing-press
Use when the user asks to retro, run a retrospective, file findings, or improve the Printing Press after a printed-CLI run. Trigger phrases: "retro", "retrospective", "what went wrong", "improve the press", "post-mortem", "lessons learned", "what can we improve", "file a retro", "submit findings". Do not use for printed-CLI polish or a single-CLI fix.
printing-press-reprint
mvanhorn/cli-printing-press
Regenerate an existing printed CLI from scratch under the current Printing Press, with prior research, prior novel features, and prior patches (post-publish hand-fixes) carried into the writing pipeline as reconciliation context rather than dropped on the floor. Pulls the CLI from the public library if it isn't local, recommends reuse-vs-redo of prior research based on age, then hands off to /printing-press with the right context. Use when a machine upgrade would benefit a published CLI more than manual polish. Trigger phrases: "reprint ", "regenerate ", "redo the CLI", "rebuild from scratch", "this CLI would benefit from a reprint".
printing-press-output-review
mvanhorn/cli-printing-press
Internal sub-skill: agentic review of a printed CLI's sampled command output for plausibility issues that rule-based checks can't encode (substring-match relevance, format bugs, silent source drops, ranking failures). Invoked via the Skill tool by the main printing-press skill at Phase 4.85 and printing-press-polish SKILL.md during the diagnostic loop. Not for direct user invocation — its actionable wrappers are /printing-press and /printing-press-polish.
Popular backend & apis skills
find-skills
vercel-labs/skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
entra-app-registration
microsoft/azure-skills
Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.
google-agents-cli-adk-code
google/agents-cli
This skill should be used when the user wants to "write agent code", "build an agent with ADK", "add a tool", "create a callback", "define an agent", "use state management" — in a project that needs ADK (Agent Development Kit) API patterns and code examples. It provides a quick reference for agent types, tool definitions, orchestration patterns, callbacks, state management, the graph Workflow API, and reference recipes to study. Do NOT use for scaffolding (use google-agents-cli-scaffold) or deployment (use google-agents-cli-deploy).
embedded-captions
heygen-com/hyperframes
Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet anchor rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.
entra-agent-id
microsoft/azure-skills
Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmipath token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registration (use entra-app-registration), Microsoft Foundry agent authoring (use microsoft-foundry).
neon
neondatabase/agent-skills
Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, the AI Gateway, and Realtime. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASEURL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Child skill neon-realtime wins for live queries in reactive apps and agents. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, realtime, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database.