Skills mvanhorn cli-printing-press CLI Printing Press
printing-press-retro
- Use it when:
- A Printing Press run hit friction and you want the press itself fixed, not only the CLI it printed.
- It does:
- Reads the run's manuscripts and the session, drops one-off, per-CLI and vendor-quirk noise, and keeps defects that would recur across CLIs.
- You get:
- A scrubbed retro document in the run's manuscripts and /tmp, and public GitHub issues on mvanhorn/cli-printing-press, only for P1 or P2 defects.
- Asks first:
- Before filing issues or uploading to catbox.moe, a public file host; you can keep the retro local instead.
- Unlike printing-press-polish:
- That one fixes the printed CLI; this one never edits the CLI or the press's source.
- Needs:
- The GitHub CLI; not the cli-printing-press binary.
Skill 9 of 9 in the CLI Printing Press bundle, after printing-press-reprint.
Only works inside its bundle: Only reviews printing-press runs, reading their manuscripts. On Submit it files public issues on mvanhorn/cli-printing-press and uploads scrubbed zips to catbox.moe, a public file host. Install CLI Printing Press instead.
On Submit, it files public issues on mvanhorn/cli-printing-press and uploads the scrubbed retro and scrubbed zips of the manuscripts and CLI source to catbox.moe, a public file host. Needs the GitHub CLI signed in.
TL;DR
The feedback loop of CLI Printing Press, for the people who change the press: its generator, scorer, skills and binary. It picks the run from your manuscripts, gathers the research brief, absorb manifest, shipcheck proof, logs and generated CLI, and mines the session, live or from its saved transcript, for errors, manual edits, hand-built features, recurring friction and score penalties, checking penalties against the scorer's code first. Most candidates are meant to die in triage: iteration noise, fixes for one CLI, vendor API quirks, one-off observations and repeats of findings two earlier retros raised. A survivor must be evidenced in three named APIs and is ranked P1 (the printed CLI is broken or unsafe) or P2 (a generalizing defect in a working CLI), with no P3. The retro lists findings, skips, drops and what the press got right, and is scrubbed of secrets and personal data, stopping for hand redaction if a vendor token remains. On Submit it files each finding to act on as a public labelled issue on mvanhorn/cli-printing-press, or comments on a matching open one, and uploads scrubbed zips of the manuscripts and CLI source, and the retro itself, to catbox.moe, a public file host.
Summarizes the skill at 94ce80e.
npx skills add https://github.com/mvanhorn/cli-printing-press --skill printing-press-retro skills.sh pageSource on GitHubAll skills from mvanhorn/cli-printing-press
Fewer weekly downloads than 80% of skills
Weekly values
| Week to | Installs |
|---|---|
| Sep 21 | 110 |
| Sep 28 | 87 |
| Oct 5 | 106 |
| Oct 12 | 94 |
| Oct 19 | 112 |
| Oct 26 | 102 |
| Nov 2 | 85 |
| Nov 9 | 98 |
Fewer downloads than 67% of skills
Fewer stars than 56% of repos
Newer than 61% of skills
| Category |
Find root causes, review code and test what you built. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills. |
|---|---|
| Type |
A multi-step process the agent follows: interview, debug, run a TDD loop, review. |
| Effect |
Its own steps change something outside your machine: post, send, deploy, provision, file issues, drive a website, or upload data to a service. |
| Needs |
A specific command-line tool or desktop app must be installed, such as gh, agent-browser, LibreOffice, Obsidian or a vendor CLI. Reads or writes an issue tracker, GitHub Issues by default. |
| Publisher |
A verified publisher on skills.sh, or the company or maintainer behind the product the skill operates. |
| Topics | |
| Stack |
SKILL.md
From mvanhorn/cli-printing-press at 94ce80e. Checked daily, last changed Nov 6, 2026.
Frontmatter
name: printing-press-retro
description: >
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.
version: 0.1.0
allowed-tools:
- Bash
- Read
- Glob
- Grep
- Write
- Agent
- AskUserQuestion
created_by: user/printing-press-retro
Result: A scrubbed retro document and, when the issue gate passes, GitHub issues for Printing Press defects only.
Next consumer: A maintainer or agent who will change the Printing Press (generator, scorer, skills, or binary) — not the printed CLI that just shipped.
Done: The manuscript proof exists and is scrubbed; every work unit is file-new, comment-on-existing, or local-only; no unredacted secret or PII remains; the user has the outcome list.
Intent: "Raised the floor" is analysis language, not a filing bar. File only when the Printing Press must change to stop a current, reproducible, generalizing P1 or P2 defect. Manual iteration on one CLI is expected work, not a finding. In user-facing output say "the Printing Press"; name the subsystem when pointing at a fix.
Boundaries
- Redact every real secret and PII before quoting. Issue bodies and retro docs are public. Use references/secret-scrubbing.md Layer 0. Never quote a leaked value as evidence of the leak.
- Don't change the machine by default. The burden of proof is on the finding.
- No P3. File only P1/P2. Anything else is Skip or Drop, not a low-priority issue. The issue gate files P1/P2 Do work units only.
- Never upload unscrubbed artifacts. Never modify manuscript or library source trees; scrub copies only.
Authority
Invocation authorizes reading manuscripts/library and writing the retro proof plus scratch copies. It does not authorize GitHub filing or public upload until the user confirms Submit. It does not authorize edits to the printed CLI or to Printing Press source.
Steps
Read references/run-resolution.md first. It
resolves $API_NAME, $RUN_ID, $RUN_DIR, $CLI_DIR, and $IN_REPO.
Never execute a phase from memory. When you enter a phase, Read its file from phases/ first.
Follow each file's final Next: pointer. Late procedure lives in the phase
file or a role-named reference it loads
(references/artifact-packaging.md,
references/issue-template.md,
references/secret-scrubbing.md). Do not
restate those files here.