打磨生成的CLI以通过验证并达到发布就绪状态。运行诊断（dogfood、verify、scorecard、go vet、gosec），自动修复所有问题（验证失败、静态分析发现、死代码、描述、README、MCP工具质量），报告前后差异，并提供发布选项。
该技能专为使用CLI生成工具（如printing-press）的开发工作流设计，用于自动将生成的CLI从初始原型打磨至发布就绪状态。它会执行一系列诊断检查，包括dogfood测试、verify验证、scorecard评分、go vet代码审查和gosec安全扫描，全面评估CLI质量。技能会自动修复所有识别出的问题，包括验证失败、静态分析发现、死代码、不准确的描述、README文档以及MCP工具质量问题。完成修复后，技能会生成前后差异报告，帮助开发者直观了解改进效果，并提供一键发布选项。支持CLI工作流自动化，适用于任何在$PRESS_LIBRARY/目录下的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工具质量），报告前后差异，并提供发布选项。在任何 /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.