skill-issue — skill activation audit

Overview

A coding agent decides which skill to run from each skill's always-on name + description. A skill can be perfectly implemented and still never fire because its description is too vague to match how people phrase requests, or because a more specific sibling silently wins. skill-issue audits exactly that surface, grading each skill A–F, simulating which skill fires for a given prompt, and reporting collision clusters where one skill shadows another.

When to Use This Skill

• Use when a skill you wrote never seems to trigger and you don't know why
• Use when the user says "why isn't my skill firing", "which skill fires for X", or "audit my skills"
• Use after writing or installing a new SKILL.md, to confirm it will actually be picked
• Use in CI to fail a PR that adds a skill with empty/duplicate/colliding metadata

How It Works