생성된 CLI를 검증 통과 및 배포 준비 상태로 다듬습니다. 진단 실행(도그푸드, 검증, 스코어카드, go vet, gosec) 후 모든 문제를 자동 수정하고, 전/후 차이를 보고하며 배포를 제안합니다.
이 스킬은 `printing-press`로 생성된 CLI 도구를 검증 및 배포 가능한 상태로 자동 정리해주는 유틸리티입니다. 주요 기능으로는 dogfood, verify, scorecard, go vet, gosec 등 여러 진단 도구를 실행하고, 검증 실패, 정적 분석 결과, 데드 코드, 설명 부족, README 오류, MCP 도구 품질 등을 포함한 모든 발견된 문제를 자동으로 수정합니다. 또한 수정 전후의 상태 변화(델타)를 보고하고, 최종적으로 publish할지 여부를 사용자에게 제안합니다. 이 스킬은 `mvanhorn/printing-press`와 함께 사용하도록 설계되었으며, `$PRESS_LIBRARY/` 디렉토리의 CLI에도 적용할 수 있습니다. 플랫폼 독립적인 Markdown 기반으로 동작하며, 'polish', 'improve the CLI', 'fix verify', 'make it publish-ready', 'clean up the CLI', 'get this ready to ship' 등의 트리거 문구로 호출할 수 있습니다.
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를 검증 통과 및 배포 준비 상태로 다듬습니다. 진단(도그푸드, 검증, 스코어카드, 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.