printing-press-import
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".
Install
git clone https://github.com/mvanhorn/cli-printing-press /tmp/cli-printing-press && ln -s /tmp/cli-printing-press/skills/printing-press-import ~/.claude/skills/printing-press-importFrom README
/printing-press-import Bring a published CLI from the public library (mvanhorn/printing-press-library) into the internal library at $PRESSLIBRARY/ 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 You want a clean baseline before running polish on a published CLI If the user is asking to polish a CLI and mentions "in/from the public library" or "from the repo", suggest running this skill first.
More from this repo
printing-press
Set up a new integration, connector, or CLI binding for any API.
printing-press-amend
Amend a published CLI from one of two input sources: (1) dogfood mode mines the active Claude Code session transcript...
printing-press-output-review
Internal sub-skill: agentic review of a printed CLI's sampled command output for plausibility issues that rule-based...