printing-press-reprint

What problem does it solve?

This Skill eliminates the risk of losing critical prior work—including research, post-publish patches, and custom features—when regenerating an existing published CLI after a Printing Press upgrade, new MCP surface launch, or when a systemic gap in the existing CLI requires a full rebuild instead of manual polish.

Core Features & Use Cases

• Version Reconciliation: Automatically checks local and public library versions of the target CLI to avoid overwriting unpublished work or importing outdated public copies.
• Research & Patch Preservation: Carries forward prior research and post-publish hand-fixed patches as context for the regeneration pipeline, preventing silent regressions of live-validated fixes.
• Recency-Aware Recommendations: Evaluates the age of prior research to recommend reusing existing work or redoing research from scratch, based on how likely the underlying API has changed.
• Use Case: If you have a published cal.com CLI that was built before a new MCP intent surface launched, this skill will pull the prior CLI, surface any existing patches for auth quirks, and hand off to the Printing Press pipeline to regenerate it with all relevant context preserved.

Quick Start

Use the printing-press-reprint skill to regenerate your existing published Notion CLI, carrying over all prior research and patches to avoid losing work.