Printing Press RetroSAFE
Every API has a secret identity. This finds it, absorbs every feature from every competing tool, then builds the GOAT CLI — designed for AI agents first, with SQLite sync, offline search, and compound insight commands.
Overview
Every API has a secret identity. This finds it, absorbs every feature from every competing tool, then builds the GOAT CLI — designed for AI agents first, with SQLite sync, offline search, and compound insight commands.
8901b29986beOBSERVED · 2026-10-28Host compatibility
What the documentation claims. We have not run a compatibility test.
| Host | Status | Notes |
|---|---|---|
| claude-code | mentioned | |
| cursor | mentioned |
What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- 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](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](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](phases/01-gather-evidence.md) | | 2 | [phases/02-mine-the-session.md](phases/02-mine-the-session.md) | | 3 | [phases/03-triage-candidates.md](phases/03-triage-candidates.md) | | 4 | [phases/04-classify-findings.md](phases/04-classify-findings.md) | | 5 | [phases/05-prioritize.md](phases/05-prioritize.md) | | 6 | [phases/06-write-the-retro.md](phases/06-write-the-retro.md) | | 7 | [phases/07-plannable-work-units.md](phases/07-plannable-work-units.md) | | 8 | [phases/08-issue-gate.md](phases/08-issue-gate.md) | | 9 | [phases/09-package-upload-present.md](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/artifact-packaging.md), [references/issue-template.md](references/issue-template.md), [references/secret-scrubbing.md](references/secret-scrubbing.md)). Do not restate those files here.
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | NA |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
8901b29986befull audit observations/trust-audit/skill/mvanhorn__printing-press-retro.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-28 | 8901b29986be | SAFE | B | 89 | first audit |
Questions
What does the printing-press-retro — mvanhorn/cli-printing-press skill do?
Every API has a secret identity. This finds it, absorbs every feature from every competing tool, then builds the GOAT CLI — designed for AI agents first, with SQLite sync, offline search, and compound insight commands.
Is printing-press-retro — mvanhorn/cli-printing-press safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can printing-press-retro — mvanhorn/cli-printing-press access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
Which assistants does printing-press-retro — mvanhorn/cli-printing-press work with?
Its documentation mentions claude-code and cursor. That is what the text claims, not a compatibility test we ran.
How current is this page?
The grade is for one exact copy of the source (8901b29986be), read on 2026-10-28. The repository is watched, and a new audit runs when it changes — this is the first audit.
Add this badge to your README
Shows this page's audit result and links back to it. It updates when the audit does.
[](https://modelsatlas.com/skills/mvanhorn/printing-press-retro/)
Not your listing, or something out of date? Claim or update your listing.