Evaluate Skill

Use this skill when the target is a local skill directory or SKILL.md file.

Workflow

Treat "Evaluate this skill." as the default entrypoint.
If the user names a skill instead of giving a path, resolve it locally first, preferring ~/.codex/skills/<skill-name> and then repo-local skills/<skill-name>.
If the user says the request in natural language first, use plugin-eval start <skill-path> --request "<user request>" --format markdown to show the routed path clearly.
Run plugin-eval analyze <skill-path> --format markdown.
Review At a Glance, Why It Matters, Fix First, and Recommended Next Step before drilling into details.
Explain which findings are structural, which are budget-related, and which are code-related.
If the user asks for an "analysis" of the skill, do not stop at the report. Also run plugin-eval init-benchmark <skill-path> and show the setup questions for refining the starter scenarios in .plugin-eval/benchmark.json.
If the user wants real usage numbers, switch to "Measure the real token usage of this skill." and run the benchmark flow.
After observed usage is available, use plugin-eval measurement-plan <skill-path> --observed-usage <usage.jsonl> --format markdown to recommend what to instrument or improve next.
If the user wants a rewrite plan, route to ../improve-skill/SKILL.md.