mvanhorn/cli-printing-press
9 skills42.7k installs38.6k starsGitHub
Install
npx skills add https://github.com/mvanhorn/cli-printing-pressSkills in this repo
1Printing Pressprinting-press encodes the CLI Printing Press novel-features absorb rubric for scoring candidate commands before code generation. It applies kill checks for LLM-only features, external services, missing auth, scope creep, poor verifiability, and fake API reimplementation, then scores survivors on domain fit, user pain, build feasibility, and research backing. Survivors need a one-sentence buildability proof naming a real API endpoint or local data source. Output uses a transcendence table with feature, command, score, buildability tag spec-emits or hand-code, evidence citations, and optional Long Description for sibling disambiguation. Reprint rules reload prior research.json to re-score shipped versus planned novel features. See SKILL.md for setup, examples, and guardrails before production use. See SKILL.md for setup, examples, and guardrails before production use. See SKILL.md for setup, examples, and guardrails before production use.5.2kinstalls2Printing Press PublishThe printing-press-publish skill publishes generated CLIs from the local Printing Press library to the public printing-press-library repo as pull requests. It requires direct user invocation, resolves API slugs from library list JSON, runs publish validate and a publish-time live dogfood gate, manages scoped git clones with fork or push access, packages via cli-printing-press publish package, preserves release ledgers on reprints, detects name collisions with update replace or alongside paths, and opens PRs without hand-editing registry.json or cli-skills mirrors. Blocked API journal mode records held APIs in blocked-apis.json only. Secret scans include vendor-prefix token detection and PII pattern scrubbing before public commits. After PR creation, agents drive Greptile review and CI to stable green without merging. Setup captures PRINTING_PRESS_BIN absolute path and enforces min-binary-version 4.0.0 compatibility before any publish steps proceed.4.9kinstalls3Printing Press PolishThe printing-press-polish skill improves generated CLIs until they pass verification and become publish-ready. It runs in a forked context so diagnostic loops stay scoped. Resolve CLI paths from slug, binary name, or absolute path under PRINTING_PRESS_HOME library, with lock-status checks to avoid overwriting active builds. Diagnostics include dogfood, verify, scorecard, go vet, and gosec, followed by automatic fixes for verify failures, static analysis, dead code, descriptions, README, and MCP tool quality. STANDALONE_MODE is true for slash-command invocation or --standalone flag; mid-pipeline callers from printing-press Phase 5.5 default to no publish offer. Phase 3 gate bundle fields can force ship_recommendation hold for missing transcendence rows. After polish, standalone runs may offer publish via AskUserQuestion but never from chained polish Publish Offer answers. Public-library polish requests suggest import first when the CLI is not local. Reports before and after scorecard and verify deltas.4.9kinstalls4Printing Press ReprintThe printing-press-reprint skill regenerates an existing printed CLI under the current Printing Press machine while carrying prior research, novel features, and post-publish patches into the writing pipeline as reconciliation context. It pulls the CLI from the public library when missing locally, recommends reuse versus redo of prior research based on age, then hands off to /printing-press so novel-features can keep, reframe, or drop prior capabilities with explicit reasons. Trigger phrases include reprint, regenerate, redo the CLI, and rebuild from scratch when a machine upgrade would help more than manual polish. Setup resolves PRESS_HOME, library and manuscript paths, and prefers a caller-supplied printing_press_bin during mid-pipeline runs. Contrast with /printing-press-polish for one-off fixes that skip research and full rebuild. Use when MCP intent surfaces, auth modes, transport, or scoring rubric changes would materially improve a published CLI rather than spot edits alone.4.8kinstalls5Printing Press ImportThe printing-press-import skill Bring a published CLI from the public library into the internal libraryso 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 youdon'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".. /printing-press-import Bring a published CLI from the public library ([`mvanhorn/printing-press-library`](https://github.com/mvanhorn/printing-press-library)) into the internal library at `$PRESS_LIBRARY/` so it matches the form the generator would produce. Manuscripts ride along. The internal library is the working copy; the public library is the durable artifact. After import, the CLI is ready for polish, emboss, or re-publish — the publish step will re-apply the module path rewrites. When to run - The public library has a CLI you don't have locally - The internal copy is broken, lost, or out of sync - You4.8kinstalls6Printing Press ScoreThe printing-press-score skill Score a generated CLI against the Steinberger bar, compare two CLIs side-by-side. /printing-press-score Score generated CLIs against the Steinberger bar. Supports rescoring, scoring by name/path, and comparing two CLIs. Quick Start Prerequisites - Go 1.26.4 or newer installed - `cli-printing-press` binary on PATH (install with `go install github.com/mvanhorn/cli-printing-press/v4/cmd/cli-printing-press@latest`) Step 0: Setup Before any other commands, run the setup contract to verify the cli-printing-press binary is on PATH and initialize scope variables: <!-- PRESS_SETUP_CONTRACT_START --> <!-- PRESS_SETUP_CONTRACT_END --> After running the setup contract, capture the `PRINTING_PRESS_BIN=<abs-path>` line from stdout. **Every subsequent `cli-printing-press ...` invocation in this skill must use that absolute path** (substitute Agents should read SKILL.md quick start steps, verify required binaries and environment variables, and follow reference files for exact parameters before calling tools. The workflow includes decision gates, anti-patterns, and cross-links to sibling skills so agents stay aligned with upstream documentation rather than improvisin.4.8kinstalls7Printing Press RetroThe printing-press-retro skill Run a retrospective after generating a CLI. Identifies systemic improvementsto the Printing Press — templates, Go binary, skill instructions, catalog —so the next CLI comes out better. Creates a GitHub issue with actionablefindings when there are Printing Press fixes to make.Use after any /printing-press run.Trigger phrases: "retro", "retrospective", "what went wrong", "improvethe press", "post-mortem", "lessons learned", "what can we improve","file a retro", "submit findings".. /printing-press-retro Analyze a Printing Press session to find ways to improve the system that produces CLIs — the Go binary, templates, skills, and catalog. Not fixes to the specific CLI that was just printed, but improvements so the *next* CLI comes out stronger. **It is a non-goal for the Printing Press to produce flawless CLIs without manual tweaks.** That's the nature of the system. We expect agents to reason over the generated CLI, customize for the specific API, build novel features, and iterate. Some hand-built work in every run is4.8kinstalls8Printing Press Output ReviewThe printing-press-output-review skill Internal sub-skill: agentic review of a printed CLI's sampled command output forplausibility issues that rule-based checks can't encode (substring-matchrelevance, format bugs, silent source drops, ranking failures). Invoked via theSkill tool by main printing-press SKILL.md (Phase 4.85) and printing-press-polishSKILL.md during the diagnostic loop. Not for direct user invocation — itsactionable wrappers are /printing-press and /printing-press-polish.. printing-press-output-review (internal) Review the sampled outputs from a printed CLI for plausibility bugs that dogfood, verify, and the rule-based `scorecard --live-check` rules can't catch. Wave B policy: all findings surface as warnings, never errors. This skill is **internal-only** (`user-invocable: false`). It's invoked by parents — main printing-press skill at shipcheck Phase 4.85, polish skill during its diagnostic loop. Running it standalone would produce floating findings text with no ship verdict, no fixes applied, no publish offer; the actionable wrappers are `/printing-press` and `/printing-press-polish`. The skill carries `context: fork` so the4.7kinstalls9Printing Press Amendprinting-press-amend turns real CLI usage friction into pull requests for published printing-press library CLIs. Two input modes feed a unified finding list: dogfood mode mines the active Claude Code session transcript for missing flags, hand-rolled API payloads, and silent-null returns, while direct-input mode accepts explicit rename, add, fix, or sniff requests with optional site endpoint discovery. Phase 0 detects MODE as dogfood, direct, both, or asks the user when ambiguous, persisting mode.txt under PRESS_RUNSTATE. Setup runs the PRESS_SETUP_CONTRACT to resolve PRINTING_PRESS_BIN absolute path, enforce min-binary-version 4.0.0, and hard-stop below the published currency floor from supported-versions.txt. Phase 1 captures typed findings with id, kind, category, classification, evidence, target_cli, rationale, and provenance, then later phases plan, execute fixes autonomously, scrub PII, and open a PR with two user checkpoints after scope capture and before PR draft. Patches track in the library .printing-press-patches directory, distinct from the binary patch subcommand AST injection. Sibling skills publish, polish, and retro cover other lifecycle stages not addressed here.3.8kinstalls