AGENT SKILL

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.

License 许可
MIT
所属仓库
filippolmt/skills
最近更新
2026-11-14
Stars
★ 1
Forks
0

01 前言 Front Matter

name
printing-press
version
3.0.0
created_by
user
description
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.
allowed-tools
[ "Bash", "Read", "Write", "Edit", "Glob", "Grep", "WebFetch", "WebSearch", "AskUserQuestion", "Agent" ]
min-binary-version
4.35.4

02 资源文件 46

03 SKILL.md 正文

/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 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.

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.

04 同仓库更多 Skills

filippolmt
filippolmt/skills

writing-for-agents

Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

★ 1
filippolmt
filippolmt/skills

wrangler

Run or troubleshoot Wrangler CLI commands in projects that have a wrangler.jsonc, wrangler.json, or wrangler.toml file, including local development, Previews, deployment, and resource management. For new projects and projects without a Wrangler configuration file, use the cf CLI instead.

★ 1
filippolmt
filippolmt/skills

workers-profiling

Profile or debug CPU usage and memory allocation in deployed Cloudflare Workers and Durable Objects. Then use this information to optimize your code.

★ 1
filippolmt
filippolmt/skills

workers-development

Run, inspect, and debug Cloudflare Workers during local development with cf dev, wrangler dev, or the Cloudflare Vite plugin, using Local Explorer to read and seed binding data and query local traces and logs. Also routes production debugging to Workers observability. Use for debugging requests whether or not the project uses Wrangler.

★ 1
filippolmt
filippolmt/skills

workers-best-practices

Cloudflare Workers best practices for production applications. Use when writing, reviewing, or configuring Workers.

★ 1
filippolmt
filippolmt/skills

wordpress-pro

Develops custom WordPress themes and plugins, creates and registers Gutenberg blocks and block patterns, configures WooCommerce stores, implements WordPress REST API endpoints, applies security hardening (nonces, sanitization, escaping, capability checks), and optimizes performance through caching and query tuning. Use when building WordPress themes, writing plugins, customizing Gutenberg blocks, extending WooCommerce, working with ACF, using the WordPress REST API, applying hooks and filters, or improving WordPress performance and security.

★ 1