printing-press-retro

Q: How do I install printing-press-retro?

Run npx skills add https://github.com/mvanhorn/cli-printing-press --skill printing-press-retro 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-retro/ (personal) or .claude/skills/printing-press-retro/ (project).

by mvanhorn

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.

Installs: 6.5K
Last 24h: +16
Trending rank: #6701
Security: Warn

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/mvanhorn/cli-printing-press --skill printing-press-retro

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

Gen Agent Trust Hub PassSAFE ·The skill performs automated retrospectives and logs issues to a GitHub repository. It includes data exposure risks due to uploading project artifacts to a public anonymous file-sharing service, along with an indirect prompt injection surface from parsing raw session transcripts.

Socket Warn1 alert: gptAnomaly

Snyk PassLOW ·Risk: LOW · No issues

SKILL.md

The instructions your agent reads when the skill is triggered.

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

Step	File
1	phases/01-gather-evidence.md
2	phases/02-mine-the-session.md
3	phases/03-triage-candidates.md
4	phases/04-classify-findings.md
5	phases/05-prioritize.md
6	phases/06-write-the-retro.md
7	phases/07-plannable-work-units.md
8	phases/08-issue-gate.md
9	phases/09-package-upload-present.md

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.

FAQ

What does the printing-press-retro skill do?

How do I install printing-press-retro?

Run npx skills add https://github.com/mvanhorn/cli-printing-press --skill printing-press-retro 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-retro/ (personal) or .claude/skills/printing-press-retro/ (project).

Which AI agents can use printing-press-retro?

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-retro safe to install?

Security partners have reviewed it: Gen Agent Trust Hub passed; Socket flagged items to review; Snyk passed. As with any skill, read the SKILL.md and bundled scripts before installing.

Who maintains printing-press-retro?

It is published by mvanhorn in mvanhorn/cli-printing-press. It has 6,507 recorded installs.

More from mvanhorn/cli-printing-press

View all →

printing-press

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

Backend & APIs7.6K installs

printing-press-publish

mvanhorn/cli-printing-press

Publish a generated CLI to the printing-press-library repo

6.9K installs

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

AI & Agents6.9K installs

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

Marketing & SEO6.5K installs

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

Backend & APIs6.5K installs

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.

Code Quality & Workflow6.4K installs

Popular other skills

View category →

hyperframes-cli

heygen-com/hyperframes

The HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.

1.3M installs