生成されたCLIを検証に通過させ、公開可能な状態に磨き上げます。診断（dogfood、verify、scorecard、go vet、gosec）を実行し、すべての問題（検証失敗、静的解析結果、デッドコード、説明文、README、MCPツール品質）を自動修正し、before/afterの差分を報告し、公開を提案します。
mvanhorn/printing-press-polish は、`/printing-press` で生成されたCLIや `$PRESS_LIBRARY/` 内の任意のCLIを、検証に合格し、公開可能な状態に自動的に磨き上げるAIエージェントスキルです。このスキルは、dogfood、verify、scorecard、go vet、gosec などの診断ツールを実行し、検証の失敗や静的解析の結果、デッドコード、説明文の不完全さ、READMEの品質、MCPツールの質など、さまざまな問題を自動的に修正します。修正後には、before/afterの差分レポートを提供し、必要に応じて公開プロセスを開始するかどうかをユーザーに提案します。主にClaude Code、Cursor、CodexなどのAIエージェントプラットフォームでの使用を想定しており、「polish」「improve the CLI」「fix verify」「make it publish-ready」などのトリガーフレーズで起動できます。開発者は、このスキルを `/printing-press` 実行後の後処理、あるいは既存のCLIの品質向上のために利用することで、手動での修正作業を大幅に削減できます。
npx skills add https://github.com/mvanhorn/cli-printing-press/tree/main/skills/printing-press-polishInstalled? Explore more 研究＆データ分析 skills: affaan-m/uspto-database, affaan-m/scholar-evaluation, affaan-m/literature-review · View all 6 →
生成されたCLIを検証に通過させ、公開可能な状態に磨き上げます。診断（dogfood、verify、scorecard、go vet、gosec）を実行し、すべての問題（検証失敗、静的解析結果、デッドコード、説明文、README、MCPツール品質）を自動修正し、before/afterの差分を報告し、公開を提案します。/printing-press の実行後、または $PRESS_LIBRARY/ 内の任意のCLIに対して使用します。トリガーフレーズ：「polish」「improve the CLI」「fix verify」「make it publish-ready」「clean up the CLI」「get this ready to ship」。
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.
Publish a generated CLI to the printing-press-library repo
Regenerate an existing printed CLI from scratch under the current Printing Press, with prior research, prior novel features, and prior patches (post-publish hand-fixes) carried into the writing pipeline as reconciliation context rather than dropped on the floor. Pulls the CLI from the public library if it isn't local, recommends reuse-vs-redo of prior research based on age, then hands off to /printing-press with the right context. Use when a machine upgrade would benefit a published CLI more than manual polish. Trigger phrases: "reprint <api>", "regenerate <api>", "redo the <api> CLI", "rebuild <api> from scratch", "this CLI would benefit from a reprint".
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.