Revisor de Skills

Point the reviewer at your skill directory and it reads the SKILL.md frontmatter and body, checks required fields like name and description, evaluates activation phrases, and returns a structured report with severity-categorized issues and specific fixes.

A good description uses third person ("This skill should be used when..."), includes specific trigger phrases users would actually say, stays between roughly 50 and 500 characters, and describes concrete scenarios rather than vague capabilities.

The body should be between 1,000 and 3,000 words. Content beyond that should be moved into references/ or examples/ directories so the main file stays concise and focused, following progressive disclosure principles.

Move detailed documentation to references/ and working code samples to examples/ when the main SKILL.md grows too long. The SKILL.md should only hold essential instructions and clearly point to these supporting files.

It checks for vague activation descriptions, second-person phrasing, missing trigger phrases, oversized SKILL.md files, missing frontmatter fields, and absent supporting files. Issues are categorized as critical, major, or minor with prioritized recommendations.