skill:critique

Skill to critique: $ARGUMENTS

Step 0: Resolve Target

Inspect $ARGUMENTS:

• Empty — ask: "Which skill should I critique? Provide a path (e.g. skills/dev-plan/SKILL.md) or a skill name (e.g. dev:plan)."
• Path to SKILL.md — read it directly; if the file does not exist, report "Cannot find SKILL.md at that path" and stop
• Skill directory — look for SKILL.md inside it
• Skill name (e.g. dev:plan, skill-review) — search skills/, .claude/skills/, and plugins/*/skills/ for a match; if multiple matches, list them and ask which one; if no match, report the unresolved name and stop

Once resolved, read the SKILL.md in full before proceeding.

Step 1: Understand the Skill's Intent

Before scoring anything, state in one sentence what this skill is trying to do and what its primary output is. This anchors the critique — every finding should connect back to whether the skill achieves that intent.

Step 2: Evaluate Each Dimension