skill-issue
Find out why a coding-agent skill won't fire — grade each SKILL.md A–F on activation, simulate which skill a prompt triggers, and flag collisions where one silently shadows another.
Profile →npx skills add sickn33/agentic-awesome-skills --skill skill-issue --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 Install the CLI (`npm i -g @misha_misha/skill-issue`, `brew install mishanefedov/skill-issue/skill-issue`, or `npx @misha_misha/skill-issue`), then: ```bash skill-issue ~/.claude/skills # grade every skill A–F (+ collisions summary) skill-issue ~/.codex/skills --why "deploy to prod" # which skill fir
- Overview
- When to Use This Skill
- How It Works
- Examples
- Example 1: Audit installed skills
- Example 2: Diagnose a collision
- Limitations
skill-issue ~/.claude/skills # grade every skill A–F (+ collisions summary) skill-issue ~/.codex/skills --why "deploy to prod" # which skill fires for this prompt, and why skill-issue <dir> --collisions # clusters of skills that shadow each other skill-issue <dir> --fix # append a "Use when …" clause to weak descriptions skill-issue <dir> --json # machine-readable; exits non-zero on errors skill-issue ~/.claude/skills F deploy-helper ✗ no description — can never fire C shipit ! no "use when …" trigger clause A rollback-prod ✓ will fire on its triggers skill-issue ~/.claude/skills --why "deploy the app to prod"
What does the skill-issue skill do?
Find out why a coding-agent skill won't fire — grade each SKILL.md A–F on activation, simulate which skill a prompt triggers, and flag collisions where one silently shadows another.
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill skill-issue --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.