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".
The printing-press-import skill imports a published CLI from the public Printing Press library into a local internal library, restoring it to the same structure and state as a freshly generated copy. Its primary purpose is to help users recover missing, broken, lost, or out-of-sync internal CLI copies by using the published version as the source of truth. During the import process, associated manuscripts are brought along and the module path is reverted so the imported CLI is ready for further local work. This provides a clean and consistent baseline for continued development and maintenance.
The skill resolves CLI targets using the public library registry, allowing users to reference a CLI by API slug, brand name, old CLI name, or similar matching terms. It supports exact, normalized, and substring-based matching against registry entries and can prompt the user to choose among multiple candidates when necessary. The workflow relies on reference scripts for fetching, backing up, rewriting, and placing imported content into the correct internal library structure. After import, the CLI is prepared for follow-up processes such as polishing, embossing, or republishing.
This skill is intended for users who manage CLI assets within the Printing Press ecosystem and need a reliable way to synchronize local and published copies. Common scenarios include importing a CLI that does not yet exist locally, restoring a damaged internal version, or establishing a clean starting point before additional refinement. It is especially useful when working with CLIs that already exist in the public repository and need to be brought back into a local development environment.
Use it when a CLI exists in the public library but is missing locally, when a local copy is broken or lost, or when you want a clean baseline before further processing.
It resolves candidates through the public library registry using exact matches, normalized matches, and substring matching on names and descriptions.
The skill presents up to four matching candidates and asks the user to choose the correct one.
Yes. Manuscripts are imported alongside the CLI so the result matches the expected internal library structure.
The skill depends on access to the public library registry and uses the referenced scripts and configured Printing Press library paths to perform the import process.
Quick Setup:
.claude/skills/Repository
mvanhorn/cli-printing-press