skill-quality-reviewer

Reviewing a skill for ship-readiness involves analyzing trigger quality, trigger collisions, duplication risk, eval integrity, and section substance. You need the skill's SKILL.md and supporting eval files to judge whether it should ship, be revised, be rejected, or become an extension.

Trigger collision analysis compares a target skill against shipped skills to spot overlapping triggers and determine whether the right move is to extend an existing skill instead of creating a new one. It helps maintain scope discipline across the skill library.

Checking eval integrity involves verifying that the skill's evals and sections actually test the boundaries of the skill rather than repeating the workflow in name only. An eval and structure audit confirms the tests validate real scope limits.

No, a skill quality review does not require re-implementing mechanical validation. It judges quality by analyzing the skill's SKILL.md and supporting eval files directly to assess trigger quality, scope, and invocation posture.

You should extend an existing skill instead of creating a new one when overlap and duplication analysis reveals significant trigger collisions with shipped skills. This indicates the new draft's functionality overlaps heavily with existing library scope.