skills-audit

Audit SKILL.md files for duplicates, overlap, staleness, and broken cross-references.

Updated Jan 27, 2026
One-click install
npx skills add https://github.com/SmallAi-API/smaihub --skill skills-audit-smallai-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skills-audit
Source: https://github.com/SmallAi-API/smaihub/tree/main/.agents/skills/skills-audit
Command: npx skills add https://github.com/SmallAi-API/smaihub --skill skills-audit-smallai-api

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Over time a project-local skill catalog drifts: skills get duplicated, descriptions stop matching their bodies, cross-references point at renamed or deleted skills, and stale entries keep getting injected into agent context. This Skill provides a repeatable audit procedure to catch that drift before the catalog becomes confusing. ## Core Features & Use Cases - Inventory and grouping: Builds a full inventory of skills (including symlinked ones), grouped by domain, with attention to recent additions via git history. - Overlap and redundancy detection: Flags duplicate descriptions, competing triggers, and stale cross-references while listing common false positives that must not be merged. - Staleness and freshness checks: Verifies that referenced code surfaces still exist, checks living-log entries for required since/holds-while markers, and validates invocation policy metadata against the active harness. - Use Case: After a week where several skills were added or renamed, run the audit to get a report of confirmed defects and merge/delete candidates with file and line references, then optionally apply safe fixes with --apply. ## Quick Start Run a skills audit over .agents/skills and report any duplicate, overlapping, stale, or broken skills with file references.

Frequently Asked Questions about skills-audit

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

FAQPage Schema
How do I audit AI agent skill files for duplicates?

Inventory all SKILL.md files including symlinked ones, group them by domain, and compare descriptions within each group. Identical descriptions or tasks matching multiple triggers indicate duplicates, but check known false positives before merging.

How to find stale or broken skill references in a skills catalog?

Search each skill body for named cross-references and confirm the target skill still exists under its owning root, resolving renames first. Also verify that referenced code surfaces still exist using ripgrep against the source tree.

When should I run a skills audit?

Run it weekly, or after any week where more than one skill was added or renamed. Frequent catalog changes are the main driver of description drift and broken cross-references.

Should overlapping skills always be merged?

No. Many apparent overlaps are false positives, such as migration workflows versus schema authoring, or content versus internationalization mechanics. Merge only when call sites would actually load the merged skill in the same context.

Can the audit apply fixes automatically?

Yes. An audit-only run produces recommendations, but when the user authorizes fixes through --apply or ordinary language, safe changes within that scope are applied directly. Deletions still require explicit authorization covering the target.