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.
94%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
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)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.
.agents/skills/verify-printing-press/scripts/pp-verify launchThis takes about 45s with a warm Go cache. In order, it:
./cli-printing-press from ./cmd/cli-printing-pressRUN=$TMPDIR/pp-verify.XXXXXX with a decoy HOME that holds a sentinel filegenerate into $RUN/cli with all quality gates onscripts/mock_api.py on a free 127.0.0.1 port, logging every request to $RUN/req.logReady means:
generate exited 0PASS printing-press-golden-pp-cli doctor$RUN/cli/build/stage/bin/ holds both the CLI and the MCP binarypp-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.
.agents/skills/verify-printing-press/scripts/pp-verify doctor "$RUN"Read-only. It checks:
cmd/, internal/, go.mod and go.sum (uncommitted and untracked edits included) are unchanged since launchdoctor --json reports api: reachable, auth_source: env:PRINTING_PRESS_GOLDEN_API_KEY, and a config_path under the decoy HOMERun 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.
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 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 HOMEProof standards:
tools/call. Do not call generator Go functions, and do not edit the printed tree to make a drive pass.NNN-*.requests.jsonl (method, path, body, X-API-Key) plus the CLI's envelope, not only success: true.--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, or tool not found). Observe the zero; don't trust the flag name.annotations object from mcp list, not the template source.<PREFIX>_BASE_URL). Never stub inside the printed code..agents/skills/verify-printing-press/scripts/pp-verify cleanup "$RUN"Cleanup:
$RUN~/printing-press and the printed CLI's real config, data, and state dirs for files modified during the run, and writes home-escape.txt and a warning if any changed$RUN to the trashEvidence stays. Run cleanup after a failed launch too: launch prints the cleanup command when it dies. Never pkill python3 or kill by name.
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 binds 127.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 runs initialize, then tools/list (paginated) or tools/call. It inherits its environment.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.
mvanhorn/cli-printing-press
c9957c1
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.