review-skill

To audit a SKILL.md file, the Skill checks frontmatter validation, prompt structure, effectiveness, and repository alignment. It proposes fixes after each stage and pauses, requiring developer approval before applying any changes to prevent unintended modifications.

The best way to validate frontmatter and prompt structure is auditing the skill directory to check required fields, multi-stage flow, stage order, and clarity. It assesses practicality and guardrails, proposing fixes that require developer approval before they are applied.

Yes, you can audit existing skills for improvements without automatic modifications. The Skill pauses after each review stage and requires explicit developer approval before applying any proposed changes, ensuring you maintain full control over the final output.

Yes, the skill audit process checks for alignment with existing repository conventions. It reviews the skill directory to ensure consistency with existing skills, evaluates scope and guardrails, and proposes fixes that require developer approval before they are applied.

You need to run a skill quality review before committing when you want to ensure new skills meet Claude Code conventions for correctness and quality. It audits frontmatter, prompt effectiveness, and repository alignment, preventing non-standard skills from being committed.