
Printing Press Reprint
Regenerate a published Printing Press CLI from scratch while keeping prior research, novel features, and post-publish patches in the reconciliation pipeline.
Install
npx skills add https://github.com/mvanhorn/cli-printing-press --skill printing-press-reprintWhat is this skill?
- Pulls the target CLI from the public library when it is not already local
- Recommends reuse versus redo of prior research based on age
- Carries prior novel features and post-publish patches into the writing pipeline
- Explicit keep, reframe, or drop decisions with reasons—no silent drops
- Hands off to /printing-press with reconciliation context for the novel-features subagent
Adoption & trust: 2k installs on skills.sh; 3.1k GitHub stars; 1/3 security scanners passed (skills.sh audits).
Recommended Skills
Journey fit
Reprinting is primarily a rebuild of the CLI artifact when the Printing Press machine improves, which is canonical Build agent-tooling work. The skill orchestrates context for `/printing-press` and CLIs printed from APIs—not general app UI or database design.
Common Questions / FAQ
Is Printing Press Reprint safe to install?
skills.sh reports 1 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.
SKILL.md
READMESKILL.md - Printing Press Reprint
# /printing-press-reprint Regenerate an existing printed CLI under the current machine. The user gives a CLI name and (optionally) reasons for the reprint. This skill ensures the prior CLI is locally present, recommends whether to reuse or redo prior research, and hands off to `/printing-press` with the context the novel-features subagent needs to reconcile prior features against the current machine — keep, reframe, or drop with reasons, never silent. ```bash /printing-press-reprint notion /printing-press-reprint cal.com the new MCP intent surface landed and the prior CLI ships endpoint-mirror only /printing-press-reprint allrecipes ``` ## When to run - A significant Printing Press upgrade (new MCP surface, new auth modes, new transport, scoring rubric changes) would lift this CLI more than manual polish. - The published CLI ships with a known systemic gap a reprint would fix. - The user wants prior novel features re-evaluated against the current machine and current personas, not carried forward verbatim. For one-off code-quality fixes, prefer `/printing-press-polish` — it doesn't redo research or rebuild the manuscript. ## Setup ```bash PRESS_HOME="${PRINTING_PRESS_HOME:-$HOME/printing-press}" PRESS_LIBRARY="$PRESS_HOME/library" PRESS_MANUSCRIPTS="$PRESS_HOME/manuscripts" # Mid-pipeline callers may pass printing_press_bin: <abs-path> in the args # bundle. Prefer it so reprint keeps using the parent skill's preflight-selected # binary instead of re-resolving through PATH. PRINTING_PRESS_BIN="${PRINTING_PRESS_BIN:-}" if [ -z "$PRINTING_PRESS_BIN" ] && [ -n "${ARGUMENTS:-}" ]; then PRINTING_PRESS_BIN="$(printf '%s\n' "$ARGUMENTS" | sed -nE 's/^[[:space:]]*printing_press_bin:[[:space:]]*(.+)$/\1/p' | head -1)" fi if [ -z "$PRINTING_PRESS_BIN" ]; then PRINTING_PRESS_BIN="$(command -v cli-printing-press 2>/dev/null || true)" fi if [ -z "$PRINTING_PRESS_BIN" ]; then echo "cli-printing-press binary not found." echo "Install with: go install github.com/mvanhorn/cli-printing-press/v4/cmd/cli-printing-press@latest" return 1 2>/dev/null || exit 1 fi echo "PRINTING_PRESS_BIN=$PRINTING_PRESS_BIN" ``` ## Phase A — Resolve and reconcile presence Resolve the user's argument the same way `/printing-press-import` does: fetch the public library `registry.json` once, then exact → normalized → fuzzy match. The argument can be an API slug (`notion`), a brand name (`cal.com`), an old `<api>-pp-cli` form, or close enough. Capture from the matched registry entry: `API_SLUG` (from `.name`) and `LIB_PATH` (from `.path`, e.g., `library/productivity/cal-com`). Phase B uses `$LIB_PATH` for the public patches fetch. For the "present | absent" never-published row, `$LIB_PATH` stays empty — Phase B's fetch short-circuits on that. Then check what exists locally and reconcile against the public library by reading both provenance manifests' `run_id` and `generated_at`: | Local | Public registry | Action | |-------|-----------------|--------| | absent | absent | STOP — nothing to reprint; suggest `/printing-press <api>` for a fresh print | | absent | present | invoke `/printing-press-import <api>`, then continue | | present | absent | continue — n