打磨生成的 CLI，使其通過驗證並達到可發布狀態。
此技能旨在自動化打磨由 `/printing-press` 生成的 CLI 工具，確保其符合發布標準。它會執行一系列診斷檢查，包括 dogfood、verify、scorecard、go vet 和 gosec，並自動修復所有發現的問題，例如 verify 失敗、靜態分析結果、死代碼、描述、README 以及 MCP 工具品質。修復完成後，技能會產生改進前後的差異報告，並提供發布選項。此技能適用於任何位於 `$PRESS_LIBRARY/` 目錄中的 CLI，支援使用諸如「polish」、「improve the CLI」、「fix verify」、「make it publish-ready」、「clean up the CLI」、「get this ready to ship」等觸發短語。它與 /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），自動修復所有問題（verify 失敗、靜態分析結果、死代碼、描述、README、MCP 工具品質），報告改進前後的差異，並提供發布選項。請在任何 /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.