skill-audit

Audits Agent Skills directories for trigger conflicts, staleness, bloat, and broken references.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/kai-kou/gem-hunter --skill skill-audit-kai-kou
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: skill-audit
Source: https://github.com/kai-kou/gem-hunter/tree/main/.claude/skills/skill-audit
Command: npx skills add https://github.com/kai-kou/gem-hunter --skill skill-audit-kai-kou

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agent Skills collections (SKILL.md files and slash commands) degrade over time: descriptions stop triggering correctly, references to tools and docs break after renames, skills overlap in responsibility, and some become dead weight. This Skill standardizes a repeatable audit so these problems are detected with the same criteria and output format every time instead of ad-hoc manual reviews. ## Core Features & Use Cases - Mechanical reference verification: Runs tools/check_skill_references.py to validate that every path mentioned in SKILL.md, commands, and rule files actually exists in the repository, with line-level exclusion markers and a self-test mode. - Multi-perspective detection: Checks for trigger conflicts, dead skills (unreferenced and untouched for 90+ days), stale content contradicted by current lessons, bloat over 500 lines, responsibility duplication, and missing skills. - Description scoring and Issue filing: Scores each skill description out of 10 for trigger precision, then files deduplicated GitHub Issues (max 5 per run) with one root cause per Issue. - Use Case: Run a quarterly inventory of .claude/skills and .claude/commands to find two skills whose descriptions both claim the same trigger phrase, one skill referencing a deleted script, and one oversized SKILL.md, then get three ready-to-triage Issues. ## Quick Start Ask the AI to audit the Agent Skills in this repository by saying "Skill γ‚’ζ£šεΈγ—γ—γ¦" or invoking /skill-audit.

Frequently Asked Questions about skill-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit Claude Code skills for stale or broken references?β–Ό

Run the skill-audit workflow, which executes tools/check_skill_references.py to extract path mentions from SKILL.md, command files, and rule docs, then verifies each exists in the repository. Exit code 1 indicates broken links or files exceeding the bloat threshold.

How to detect trigger conflicts between multiple Agent Skills?β–Ό

Compare the description frontmatter of all skills for overlapping trigger phrases such as audit or inventory keywords. When comparison is ambiguous, actually send the trigger phrase and observe which skill fires to confirm the conflict.

What counts as a dead or abandoned skill in a repository?β–Ό

A skill is a dead-stock candidate when no other skill, rule, or harness references it and its last git commit is over 90 days old. The audit checks both conditions using Grep for references and git log for the last modification date.

Can I exclude false-positive references from the link checker?β–Ό

Yes, add a refcheck:ignore HTML comment at the end of the specific line, or wrap a range with ignore-start and ignore-end markers. Exclusions must be line-scoped because section-level exclusions can silently disable verification of valid references.

What are the limitations of the skill-audit workflow?β–Ό

It only audits the structure of Agent Skills assets, not workflow health like PR or Issue pipeline state, which belongs to workflow-health-check. Detected problems are filed as Issues rather than fixed directly, and a maximum of five Issues are created per run.