メニュー
Convert cc-plugin-eval findings into a concrete rewrite brief, then hand off to skill-creator for the edit pass. Use when the user already ran an evaluation and now wants a fix plan, after asking "what should I fix first" or "rewrite this using the findings".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Publish a Skill, config, or plugin to TomeVault as a high-grade Tome — and understand the Skill / Tome / AGENTS.md model behind it. Use when shipping instruction files to TomeVault, indexing a repo, aiming for a Gold grade, passing the TomeVault scan or validator, or answering "what is a Tome / Skill / AGENTS.md". Covers the npx tomevault CLI, the Studio web publish flow, and the grading rubric.
Ferry a GitHub PR to merge — one snapshot-not-block iteration that reads live PR state, classifies it, and runs exactly one handler: fix CI at the root cause, repair merge conflicts, triage reviewer threads with version-currency checks, rewire human-blocked reviews, or propose-and-pause before any force op. Use when asked to merge / land / babysit a GitHub PR — including plain-language 'merge my PR', 'get this branch merged', or 'babysit my PRs' with no slash command and no state file yet — or when resuming a /charon ferry, without ever waiting forever.
Use when the user needs X/Twitter data through Xquik for REST API planning, MCP setup, SDKs, search, exports, monitoring, webhooks, or confirmation-gated publishing.
Analyze CI build and test status from Azure DevOps and Helix for dotnet repository PRs. Use when checking CI status, investigating failures, determining if a PR is ready to merge, or given URLs containing dev.azure.com or helix.dot.net. Also use when asked "why is CI red", "test failures", "retry CI", "rerun tests", "is CI green", "build failed", "checks failing", or "flaky tests". DO NOT USE FOR: investigating stale codeflow PRs or dependency update health, tracing whether a commit has flowed from one repo to another, reviewing code changes for correctness or style.
Run risky changes through 8 disciplined phases that map, build, fix, and verify — each unlocks more power only if work stays honest and resumable. Use when a spec or audit needs parallel discovery, lane execution, checkpoints surviving context loss, and a ship-or-die finale.
Analyze, lint, and check a local Claude Code add-on or capability, explain the result, and rank the top fixes first. Use when the user says "audit this", "why did it score that way", "what should I fix first", "validate the manifest", "lint the hooks", or "benchmark the real token usage".
| name | improve-skill |
| description | Convert cc-plugin-eval findings into a concrete rewrite brief, then hand off to skill-creator for the edit pass. Use when the user already ran an evaluation and now wants a fix plan, after asking "what should I fix first" or "rewrite this using the findings". |
Use this skill after cc-plugin-eval has already produced findings for a local skill.
The runnable commands below invoke the shipped script through the plugin root, which works in any checkout: node "${CLAUDE_PLUGIN_ROOT}/scripts/cc-plugin-eval.js" <command> <args>. Inline mentions of cc-plugin-eval <command> are shorthand for that same invocation; the bare cc-plugin-eval alias only exists if you ran npm link in the plugin directory.
This skill does not perform LLM-driven rewrites. That is the job of the skill-creator skill (Anthropic's skill-creator@claude-plugins-official). cc-plugin-eval produces structured findings and a rewrite brief; skill-creator turns the brief into edits with subagent-driven evals and grading. Keep the two boundaries clear.
cc-plugin-eval analyze <skill-path> --brief-out ./skill-brief.json. The same payload is also produced by cc-plugin-eval improve <skill-path> --brief-out ./skill-brief.json, which writes the improvement brief as the top-level payload.error or fail) versus recommended fixes (severity warn or info).skill-creator. That skill specializes in skill rewrites with subagent-driven evals.cc-plugin-eval analyze <skill-path> --output ./after.json and use cc-plugin-eval compare ./before.json ./after.json --format markdown to measure the delta.SKILL.md compact (target under 500 lines; hard limit at 800; reference threshold is 350)allowed-tools syntax (CC215) and add disable-model-invocation to task-style skills where appropriate (CC216)Improve this skill based on the evaluation.Rewrite this skill using the cc-plugin-eval findings.What should I fix first in this skill?Hand the brief to skill-creator.node "${CLAUDE_PLUGIN_ROOT}/scripts/cc-plugin-eval.js" analyze <skill-path> --brief-out ./skill-brief.json
node "${CLAUDE_PLUGIN_ROOT}/scripts/cc-plugin-eval.js" improve <skill-path> --brief-out ./skill-brief.json --format markdown
node "${CLAUDE_PLUGIN_ROOT}/scripts/cc-plugin-eval.js" analyze <skill-path> --output ./after.json
node "${CLAUDE_PLUGIN_ROOT}/scripts/cc-plugin-eval.js" compare ./before.json ./after.json --format markdown
../../references/chat-first-workflows.md../../references/evaluation-result-schema.md