Skill Quality Review

When to use

• Review a Skill at package level rather than only polishing prose.
• Check whether SKILL.md, the primary Prompt, metadata, examples, references, and evals/ form one consistent contract.
• Assess whether a Skill can be copied or installed independently and which conclusions still lack runtime evidence.

Output format options

• Default to a Markdown review with a conclusion, blocking issues, suggestions, information gaps, and evidence boundaries.
• Use a table when several files or evidence layers must be compared; do not replace the reasoning with a score.

How to use