printing-press-import

What problem does it solve?

This Skill eliminates the manual effort of setting up published command-line interfaces (CLIs) in your local internal printing press library, whether you are missing a CLI entirely, have a broken or lost internal copy, or need a clean baseline before running polish or emboss workflows on a published tool.

Core Features & Use Cases

• Natural Language CLI Resolution: Matches user input (API slugs, brand names, old CLI names, or close approximations) to entries in the public printing press library registry to identify the correct CLI to import.
• Safe Overwrite Protection: Compares provenance data (run ID, generation timestamp) between public and internal copies to avoid clobbering in-progress work on local CLIs, and creates automatic backups before any overwrites.
• End-to-End Import Automation: Orchestrates the full import workflow including fetching the CLI from the public library, reversing public module path rewrites to match local format, placing files and associated manuscripts in the correct internal library locations, and verifying the imported CLI builds successfully with no leaked public module references.
• Use Case: If you want to run the /printing-press-polish workflow on a published Notion CLI but do not have it in your internal library, this Skill automates the entire import process so the CLI is ready for the next step.

Quick Start

Use the printing-press-import skill to bring the published cal.com CLI into your internal printing press library.