菜单
Analyze and check a local Claude Code SKILL.md folder: review frontmatter, size, broken links, trigger words, and token budget, then rank the top fixes. Use when the user says "audit this", "why did it score that way", "this is too big", "it is not triggering", or "measure the real token usage".
用 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 | evaluate-skill |
| description | Analyze and check a local Claude Code SKILL.md folder: review frontmatter, size, broken links, trigger words, and token budget, then rank the top fixes. Use when the user says "audit this", "why did it score that way", "this is too big", "it is not triggering", or "measure the real token usage". |
Use this skill when the target is a local skill directory or a SKILL.md file. cc-plugin-eval handles the structural and budget signals deterministically without an LLM. If the user wants an LLM-graded rubric or a rewrite pass, hand off to the skill-creator skill (Anthropic's skill-creator@claude-plugins-official) - that skill specializes in single-skill grading and rewrites, while cc-plugin-eval focuses on structural and budget signals.
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.
~/.claude/plugins/cache/<plugin-id>/skills/<skill-name> for installed-plugin skills, then any repo-local skills/<skill-name> directory. If the name is still ambiguous, ask one short clarifying question before running commands.cc-plugin-eval start <skill-path> --request "<user request>" --format markdown to show the routed path clearly.cc-plugin-eval analyze <skill-path> --format markdown. The convenience alias cc-plugin-eval evaluate-skill <skill-path> returns the same payload but errors out if the path is not a skill.At a Glance, Why It Matters, Fix First, and Recommended Next Step before drilling into details.cc-plugin-eval init-benchmark <skill-path> and show the setup questions for refining the starter scenarios in .cc-plugin-eval/benchmark.json.cc-plugin-eval measurement-plan <skill-path> --observed-usage <usage.jsonl> --format markdown to recommend what to instrument next.../improve-skill/SKILL.md. That skill writes a brief and hands it to skill-creator for the actual rewrite.name, description, when_to_use, argument-hint, arguments, disable-model-invocation, user-invocable, allowed-tools, model, effort, context, agent, hooks, paths, shell, license, metadata)name and description quality (CC201, CC202, CC203, CC204, CC205, CC206)>350 lines (CC208), >500 lines (CC210), >800 lines (CC209)claude://, app://, plugin://, rules://, mailto:, http://, https://, #allowed-tools syntax (CC215): Claude tool names are PascalCase (Bash, Read, Edit, Skill, mcp__server__tool); strings should be space-separated or YAML lists, not comma-separateddisable-model-invocation: true on task-style skills (CC216) where automatic invocation would be wrongEvaluate this skill.Give me an analysis of this skill.Audit this skill.Why did this skill score that way?What should I fix first?This skill is too big.This skill is not triggering.Measure the real token usage of this skill.node "${CLAUDE_PLUGIN_ROOT}/scripts/cc-plugin-eval.js" start <skill-path> --request "Evaluate this skill." --format markdown
node "${CLAUDE_PLUGIN_ROOT}/scripts/cc-plugin-eval.js" analyze <skill-path> --format markdown
node "${CLAUDE_PLUGIN_ROOT}/scripts/cc-plugin-eval.js" evaluate-skill <skill-path> --format markdown
node "${CLAUDE_PLUGIN_ROOT}/scripts/cc-plugin-eval.js" explain-budget <skill-path> --format markdown
node "${CLAUDE_PLUGIN_ROOT}/scripts/cc-plugin-eval.js" measurement-plan <skill-path> --format markdown
node "${CLAUDE_PLUGIN_ROOT}/scripts/cc-plugin-eval.js" init-benchmark <skill-path>
node "${CLAUDE_PLUGIN_ROOT}/scripts/cc-plugin-eval.js" benchmark <skill-path>
node "${CLAUDE_PLUGIN_ROOT}/scripts/cc-plugin-eval.js" analyze <skill-path> --observed-usage <usage.jsonl> --format markdown
../../references/chat-first-workflows.md../../references/component-validators.md