What problem does it solve? Publishing a generated CLI to the public printing-press-library repository involves forking, cloning, validating, live-testing, packaging, and opening a compliant pull request — a long, error-prone sequence where a single wrong file edit (like touching bot-regenerated registry files) gets the PR auto-rejected. This Skill automates the entire publish flow with the correct guards and conventions. ## Core Features & Use Cases - End-to-end publish pipeline: Resolves the CLI by name, confirms its category, runs structural validation and a live end-to-end dogfood gate, then packages and opens a PR against mvanhorn/printing-press-library. - Registry safety guards: Never edits bot-regenerated files (registry.json, README catalog cells, cli-skills mirrors) that would hard-fail the library's CI, and preserves release-ledger files when replacing an existing CLI. - Blocked API journal mode: With --blocked-api-journal, records a held generation attempt in blocked-apis.json as a journal-only PR instead of publishing a CLI. - Use Case: After generating and polishing a Notion CLI with Printing Press, run the publish skill to validate it against the live API, fork the library repo, push a branch, and open a Greptile-review-ready pull request. ## Quick Start Ask the assistant to publish the notion CLI to the printing-press-library repository as a pull request using this skill.