verify-printing-press
Skill5k starsChanged 3 days agoMITView on GitHub
Drive the real Printing Press end to end and capture proof. It builds the cli-printing-press binary, prints the golden fixture CLI into a decoy HOME, and runs the printed CLI, its MCP server, and the press's own verifiers against a request-logging mock. Use it to prove that a generator, template, MCP, or verifier change works in an emitted CLI, rather than only in Go tests or golden text.
- Reads credentials
Trending
Less talk lately.about the whole repository
Who's talking about mvanhorn/cli-printing-press
- A Hacker News story“CLI Printing Press – create go CLI tool from any API”Hacker News · May 7, 2026 · 7 points
- mvanhorn/printing-press-library“chore(cli): bump per-CLI Go floor to 1.26.11 (GO-2026-6859)”GitHub · Nov 13, 2026 · 1 reactions
- mvanhorn/printing-press-library“fix(hostex): repair sync offset, transactions range and review keys”GitHub · Oct 3, 2026 · 1 reactions
- mvanhorn/printing-press-library“fix(meta-ads): follow Graph paging.next for --all”GitHub · Sep 29, 2026 · 1 reactions
- mvanhorn/printing-press-library“fix(instagram): follow Graph cursors for media list --all”GitHub · Sep 29, 2026 · 1 reactions
The biggest 5 of 38 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 38
Talked about on GitHub, Hacker News and Bluesky (38 times).
On GitHub · 36
- Nov 13, 2026chore(cli): bump per-CLI Go floor to 1.26.11 (GO-2026-6859) — mvanhorn/printing-press-library1 reaction · 2 comments
- Oct 3, 2026fix(hostex): repair sync offset, transactions range and review keys — mvanhorn/printing-press-library1 reaction · 4 comments
- Sep 29, 2026fix(meta-ads): follow Graph paging.next for --all — mvanhorn/printing-press-library1 reaction · 1 comment
- Sep 29, 2026fix(instagram): follow Graph cursors for media list --all — mvanhorn/printing-press-library1 reaction · 1 comment
- Aug 8, 2026feat(spotify): quota circuit breaker with real Retry-After, token-stable tiered cache, adaptive rate limiting by default — mvanhorn/printing-press-library1 reaction · 1 comment
31 more on GitHub
- Jul 29, 2026feat(scrape-creators): make --all follow response cursors; add --all, aliases, positional handle to feed commands — mvanhorn/printing-press-library1 reaction · 5 comments
- Jun 27, 2026docs(plans): vibe-signal v1 build-ready spec + generation blocker — mvanhorn/printing-press-library1 reaction · 2 comments
- Jun 18, 2026ci: harden release supply chain — mvanhorn/last30days-skill1 reaction · 2 comments
- Jun 16, 2026fix(ci): bump workflow Go toolchain — mvanhorn/printing-press-library1 reaction · 1 comment
- Jun 15, 2026fix: correct go install command in CONTRIBUTING.md — mvanhorn/printing-press-library1 reaction · 1 comment
- May 9, 2026feat(fireflies): add fireflies — mvanhorn/printing-press-library1 reaction · 2 comments
- Nov 7, 2026upstream press watch: cli-printing-press fixes msp-skills is waiting on — Servosity/msp-skills0 reactions · 1 comment
- Oct 26, 2026press-watch: cli-printing-press v4.35.5 is newer than the fleet (4.35.3) — Servosity/msp-skills0 reactions
- Oct 23, 2026press-watch: cli-printing-press v4.34.0 is newer than the fleet (4.33.5) — Servosity/msp-skills0 reactions · 1 comment
- Oct 2, 2026upstream press watch: cli-printing-press fixes msp-skills is waiting on — Servosity/msp-skills0 reactions · 1 comment
- Sep 19, 2026upstream press watch: cli-printing-press fixes msp-skills is waiting on — Servosity/msp-skills0 reactions · 3 comments
- Sep 5, 2026Sweep: add QueryHash and RedactPII to published learn/recall.go — mvanhorn/printing-press-library0 reactions
- Sep 2, 2026upstream press watch: cli-printing-press fixes msp-skills is waiting on — Servosity/msp-skills0 reactions · 1 comment
- Aug 30, 2026sweep-canonical: retrofit learn identity + journal session exports — mvanhorn/printing-press-library0 reactions
- Aug 30, 2026sweep-canonical: retrofit SKILL.md Auth Setup to resolved credential env vars — mvanhorn/printing-press-library0 reactions
- Aug 16, 2026upstream press watch: cli-printing-press fixes msp-skills is waiting on — Servosity/msp-skills0 reactions · 2 comments
- Aug 14, 2026upstream press watch: cli-printing-press fixes msp-skills is waiting on — Servosity/msp-skills0 reactions · 1 comment
- Jul 8, 2026sweep: update published install guidance to Go 1.26.5 (cli-printing-press#3506) — mvanhorn/printing-press-library0 reactions · 1 comment
- Jun 7, 2026ATRPE Topic Candidates — OnlyMyRailgun/ATRPE0 reactions
- Jun 7, 2026ATRPE Topic Candidates — OnlyMyRailgun/ATRPE0 reactions
- Jun 7, 2026ATRPE Topic Candidates — OnlyMyRailgun/ATRPE0 reactions
- Jun 7, 2026ATRPE Topic Candidates — OnlyMyRailgun/ATRPE0 reactions
- Jun 7, 2026ATRPE Topic Candidates — OnlyMyRailgun/ATRPE0 reactions
- Jun 7, 2026ATRPE Topic Candidates — OnlyMyRailgun/ATRPE0 reactions
- Jun 7, 2026ATRPE Topic Candidates — OnlyMyRailgun/ATRPE0 reactions · 86 comments
- Jun 7, 2026ATRPE Topic Candidates — OnlyMyRailgun/ATRPE0 reactions · 1 comment
- Jun 7, 2026ATRPE Topic Candidates — OnlyMyRailgun/ATRPE0 reactions · 1 comment
- Jun 4, 2026Sweep-canonical + verify_skill updates for generator paths-and-state sections (cli-printing-press#2633) — mvanhorn/printing-press-library0 reactions · 1 comment
- May 26, 2026Update sweep-canonical for region and language SKILL frontmatter — mvanhorn/printing-press-library0 reactions
- May 26, 2026sweep-canonical: handle generated SKILL anti-triggers section — mvanhorn/printing-press-library0 reactions
- May 24, 2026epic: valuta PrintingPress.dev — auto-generazione MCP server e CLI agent-native da API esterne — Solarfox88/IGRIS_GPT0 reactions
On Hacker News · 1
- May 7, 2026CLI Printing Press – create go CLI tool from any API7 points
On Bluesky · 1
- May 7, 2026RT @mvanhorn: What is happening?! Printing Press is trending news on X! Please star on github both repos if you haven't yet.… — @garrytan-mir-rt.selfhosted.social0 likes and reposts · 1 reply
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- printing-press-amendSkill
- printing-press-importSkill
- printing-press-output-reviewSkill
- printing-press-polishSkill
- printing-press-publishSkill
- printing-press-reprintSkill
- printing-press-retroSkill
- printing-press-scoreSkill
- printing-pressSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 59
Run it before the first drive, again after any drive that did something surprising, and whenever you edit generator code mid-run.
- Distinctive: line 63
Every drive command saves its stdout, stderr, exit code, and the exact mock requests it caused.
- Very specific: line 130
All three are executable and live in scripts/:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Verify the Printing Press
The product surface is a CLI that produces other CLIs. A user runs cli-printing-press generate on a spec and gets a printed CLI: <api>-pp-cli, plus <api>-pp-mcp for agents. Proving a change means printing a CLI and then driving what was printed. The four surfaces, in order of how often a change touches them:
cli-printing-press generate(spec → printed CLI tree, with 9 quality gates)- The printed CLI's commands against an API
- The printed MCP server's tools and annotations
- The press's verifiers run on a printed CLI (
verify,verify-skill,scorecard,shipcheck,dogfood)
Everything goes through scripts/pp-verify (paths below are relative to this skill directory). It never touches the real ~/printing-press or the real config of a printed CLI. Each run gets its own decoy HOME, output dir, mock port, and evidence directory, so two runs can go side by side. Every drive in this skill uses the fixture testdata/golden/fixtures/golden-api.yaml, which prints printing-press-golden-pp-cli with env prefix PRINTING_PRESS_GOLDEN_.
This skill complements scripts/golden.sh verify, scripts/verify-generator-output.sh, and go test ./.... Those prove bytes and compilation. This skill proves behavior: what the printed binary actually sends, refuses, and reports.
Launch
.agents/skills/verify-printing-press/scripts/pp-verify launchThis takes about 45s with a warm Go cache. In order, it:
- builds
./cli-printing-pressfrom./cmd/cli-printing-press - creates
RUN=$TMPDIR/pp-verify.XXXXXXwith a decoy HOME that holds a sentinel file - runs
generateinto$RUN/cliwith all quality gates on - starts
scripts/mock_api.pyon a free 127.0.0.1 port, logging every request to$RUN/req.log
Ready means:
generateexited 0- its log contains
PASS printing-press-golden-pp-cli doctor $RUN/cli/build/stage/bin/holds both the CLI and the MCP binary- the mock published its port
pp-verify checks all four and prints two lines. Copy them; every later command needs RUN:
RUN=/var/folders/.../pp-verify.AbC123
EVIDENCE=<repo>/.gotmp/verify-printing-press/evidence/<timestamp>-<pid>Your real Go build and module caches are reused on purpose. The decoy HOME would otherwise force a cold build of about 5 minutes.
Doctor
.agents/skills/verify-printing-press/scripts/pp-verify doctor "$RUN"Read-only. It checks:
- the repo binary, HEAD, and the press source under
cmd/,internal/,go.modandgo.sum(uncommitted and untracked edits included) are unchanged since launch - both printed binaries are staged
- the mock PID is ours and alive, and answers on its port
- the decoy sentinel is intact
- the printed CLI's own
doctor --jsonreportsapi: reachable,auth_source: env:PRINTING_PRESS_GOLDEN_API_KEY, and aconfig_pathunder the decoy HOME
Run it before the first drive, again after any drive that did something surprising, and whenever you edit generator code mid-run. A changed binary, HEAD, or press source fails doctor: the printed CLI predates your change, so clean up and relaunch.
Drive
Every drive command saves its stdout, stderr, exit code, and the exact mock requests it caused. It also prints its own output, so you can read the result inline.
V=.agents/skills/verify-printing-press/scripts/pp-verify
# Printed CLI: clean env (env -i), decoy HOME, API key + base URL pointed at the mock
$V cli "$RUN" -- projects list --json
$V cli "$RUN" -- projects create --name Delta --visibility private --json
$V cli "$RUN" -e PRINTING_PRESS_VERIFY=1 -- projects create --name Gamma --json # extra env with -e K=V
# Printed MCP server over stdio
$V mcp "$RUN" list # tool names + annotations
$V mcp "$RUN" call projects_get '{"projectId":"proj-1"}'
$V mcp "$RUN" -e PRINTING_PRESS_GOLDEN_MCP_READ_ONLY=1 list
# The press itself, with the decoy HOME (run from repo root, relative spec paths OK)
$V press "$RUN" verify --dir "$RUN/cli" --spec testdata/golden/fixtures/golden-api.yaml --json
$V press "$RUN" verify-skill --dir "$RUN/cli"
# Everything the mock has received this run
$V requests "$RUN"To find a command or tool handle, read the printed tree's help ($V cli "$RUN" -- --help, $V cli "$RUN" -- <cmd> --help) or $V mcp "$RUN" list. Treat those, not memory, as the stable handles. The mock (scripts/mock_api.py) answers the golden fixture's routes with fixed JSON (proj-1/Alpha, task-1, USD). Any other path gets {"ok": true} with status 200.
To verify a generator change against a different spec, generate it yourself:
$V press "$RUN" generate --spec <spec> --output "$RUN/other"Then drive it with press verify --dir "$RUN/other" --spec <spec>. That uses the press's spec-derived mock. pp-verify cli and pp-verify mcp are wired only to the golden print.
Evidence
Evidence goes to $EVIDENCE, which is .gotmp/verify-printing-press/evidence/<run-id>/ in the repo (gitignored). It survives cleanup:
launch-generate.log: full generate output, including the 9 quality gate verdictsNNN-<label>.stdout,.stderr,.requests.jsonl: one set per drivetranscript.md: per drive, the command, exit code, and mock request countall-requests.jsonl: written at cleanuphome-escape.txt: present only if something wrote under the real HOME
Proof standards:
- Drive the printed binary the way a user or agent does: CLI args or MCP
tools/call. Do not call generator Go functions, and do not edit the printed tree to make a drive pass. - For a write, proof is the request in
NNN-*.requests.jsonl(method, path, body,X-API-Key) plus the CLI's envelope, not onlysuccess: true. - For a refusal or no-op (
--dry-run,PRINTING_PRESS_VERIFY=1, MCP read-only mode), proof is zero new mock requests for that drive, plus the envelope that says why (dry_run: true,verify_noop: true, ortool not found). Observe the zero; don't trust the flag name. - For an MCP annotation claim, proof is the
annotationsobject frommcp list, not the template source. - For a generator change, show the drive on a print made after the change. Doctor's binary, HEAD, and source checks enforce this.
- Mocks are acceptable only because the printed client's base URL is a production config surface (
<PREFIX>_BASE_URL). Never stub inside the printed code.
Cleanup
.agents/skills/verify-printing-press/scripts/pp-verify cleanup "$RUN"Cleanup:
- kills only the mock PID this run started, after confirming its command line references this
$RUN - copies the request log into evidence
- checks the real
~/printing-pressand the printed CLI's real config, data, and state dirs for files modified during the run, and writeshome-escape.txtand a warning if any changed - moves
$RUNto the trash
Evidence stays. Run cleanup after a failed launch too: launch prints the cleanup command when it dies. Never pkill python3 or kill by name.
Helpers
All three are executable and live in scripts/:
pp-verify: the entry point above. Run it with no arguments for usage.mock_api.py PORT_FILE REQUEST_LOG: request-logging JSON mock. It binds127.0.0.1:0, writes its port to PORT_FILE, and appends one JSON line per request.mcp_call.py MCP_BIN list | call TOOL JSON: minimal MCP stdio client. It runsinitialize, thentools/list(paginated) ortools/call. It inherits its environment.
Feature map
features/README.md is the index; read it before driving. Each feature file holds the recipe and the observable end state that proves the feature works. When a change touches a feature, drive every entry point that feature lists, not just one convenient one.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

