既存の印刷済みCLIを現在のPrinting Press下でゼロから再生成し、以前の研究成果、新機能、パッチ（公開後の手動修正）を廃棄せずに調整コンテキストとして執筆パイプラインに引き継ぎます。CLIがローカルにない場合は公開ライブラリから取得し、研究成果の年数に基づいて再利用か再実行かを推奨した後、適切なコンテキストとともに/printing-pressに引き渡します。手動による洗練よりもマシンアップグレードが公開CLIにメリットをもたらす場合に使用します。トリガーフレーズ：「<api>を再印刷」、「<api>を再生成」、「<api> CLIをやり直し」、「<api>をゼロから再構築」、「このCLIは再印刷の恩恵を受けるでしょう」。
このスキルは、既に印刷・公開されたCLIを、最新のPrinting Pressフレームワーク下で完全に再生成するためのワークフローを自動化します。以前の開発段階で収集した研究成果、実装した新機能、公開後に手動で適用されたパッチ（修正）をすべて保持し、それらを新たな執筆パイプラインの「調整コンテキスト」として活用する点が特徴です。単純な再生成ではなく、過去の成果を無駄にしないインテリジェントな再現を実現します。対象のCLIがローカル環境に存在しない場合は、公開ライブラリから自動的に取得します。さらに、研究成果の経過時間に基づいて、再利用（reuse）するか再実行（redo）するかを推奨します。その後、適切なコンテキストとともに/printing-pressスキルに処理を引き渡します。手動での修正や微調整よりも、マシンによる体系的なアップグレードが公開CLIに大きな恩恵をもたらす状況で使用することを想定しています。主なトリガーフレーズとして、「reprint <api>」、「regenerate <api>」、「redo the <api> CLI」、「rebuild <api> from scratch」、「this CLI would benefit from a reprint」が用意されています。
npx skills add https://github.com/mvanhorn/cli-printing-press/tree/main/skills/printing-press-reprintInstalled? Explore more 研究＆データ分析 skills: affaan-m/uspto-database, affaan-m/scholar-evaluation, affaan-m/literature-review · View all 6 →
既存の印刷済みCLIを現在のPrinting Press下でゼロから再生成し、以前の研究成果、以前の新機能、および以前のパッチ（公開後の手動修正）を、廃棄せずに調整コンテキストとして執筆パイプラインに引き継ぎます。CLIがローカルにない場合は公開ライブラリから取得し、研究成果の年数に基づいて再利用か再実行かを推奨し、適切なコンテキストとともに/printing-pressに引き渡します。手動による洗練よりもマシンアップグレードが公開CLIにメリットをもたらす場合に使用します。トリガーフレーズ："reprint "、"regenerate "、"redo the CLI"、"rebuild from scratch"、"this CLI would benefit from a reprint"。
This repo contains 9 individual skills — each has its own dedicated page.
Generate a ship-ready CLI for an API with a lean research -> generate -> build -> shipcheck loop.
Amend a published CLI from one of two input sources: (1) dogfood mode mines the active Claude Code session transcript for friction (missing flags, hand- rolled API payloads, silent-null returns); (2) direct-input mode accepts user-supplied asks (rename a command, add commands or feeds, fix a named bug, optionally sniff the source site for new endpoints). Confirms scope with the user, plans + executes the fix autonomously, scrubs PII, and opens a PR against mvanhorn/printing-press-library. Two user-in-loop checkpoints: scope after capture, PR draft before open. Trigger phrases: "amend the CLI", "submit a patch", "fix what I just dogfooded", "open a PR for this CLI", "patch this CLI", "add features to my CLI", "rename this command", "add these feeds to <cli>", "sniff for new APIs in <cli>", "amend with these ideas", "use printing-press-amend", "run printing-press-amend".
Browse and install pre-built Go CLIs for popular APIs from the catalog
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".
Internal sub-skill: agentic review of a printed CLI's sampled command output for plausibility issues that rule-based checks can't encode (substring-match relevance, format bugs, silent source drops, ranking failures). Invoked via the Skill tool by main printing-press SKILL.md (Phase 4.85) and printing-press-polish SKILL.md during the diagnostic loop. Not for direct user invocation — its actionable wrappers are /printing-press and /printing-press-polish.
Polish a generated CLI to pass verification and become publish-ready. Runs diagnostics (dogfood, verify, scorecard, go vet, gosec), automatically fixes all issues (verify failures, static-analysis findings, dead code, descriptions, README, MCP tool quality), reports the before/after delta, and offers to publish. Use after any /printing-press run, or on any CLI in $PRESS_LIBRARY/. Trigger phrases: "polish", "improve the CLI", "fix verify", "make it publish-ready", "clean up the CLI", "get this ready to ship".
Publish a generated CLI to the printing-press-library repo
Run a retrospective after generating a CLI. Identifies systemic improvements to the Printing Press — templates, Go binary, skill instructions, catalog — so the next CLI comes out better. Creates a GitHub issue with actionable findings when there are Printing Press fixes to make. Use after any /printing-press run. Trigger phrases: "retro", "retrospective", "what went wrong", "improve the press", "post-mortem", "lessons learned", "what can we improve", "file a retro", "submit findings".
Score a generated CLI against the Steinberger bar, compare two CLIs side-by-side
USPTO patent and trademark data workflow for official record lookup, PatentSearch queries, TSDR checks, assignment data, and reproducible IP research logs.
Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.
Systematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging.
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Agent skill repository discovered by 10x-chat research.
Review backend code for quality, security, maintainability, and best practices based on established checklist rules. Use when the user requests a review, analysis, or improvement of backend files (e.g., `.py`) under the `api/` directory. Do NOT use for frontend files (e.g., `.tsx`, `.ts`, `.js`). Supports pending-change review, code snippets review, and file-focused review.