skills-audit

Audit SKILL.md files for duplicates, stale references, and description inconsistencies.

74|11|Updated Jul 4, 2024
One-click install
npx skills add https://github.com/OpenSourceAGI/qwksearch-research-agent --skill skills-audit-opensourceagi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skills-audit
Source: https://github.com/OpenSourceAGI/qwksearch-research-agent/tree/main/apps/qwk-in-lobe/.agents/skills/skills-audit
Command: npx skills add https://github.com/OpenSourceAGI/qwksearch-research-agent --skill skills-audit-opensourceagi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? As a project accumulates agent skills under .agents/skills/, the catalog drifts: duplicate or overlapping skills appear, descriptions stop matching their bodies, and cross-references break after renames. This Skill provides a repeatable audit procedure to catch that drift before the catalog becomes confusing. ## Core Features & Use Cases - Inventory and Census: Builds a fresh count of all SKILL.md files (including symlinked ones), grouped by domain, with git history to spot new arrivals. - Overlap and Redundancy Detection: Compares descriptions and trigger keywords within each domain to flag merge or delete candidates, while listing known false positives to avoid. - Consistency and Integrity Checks: Enforces a standard description template (Use when / Triggers on), verifies referenced skills still exist, and flags stale skills whose underlying code surface is gone. - Use Case: Run a weekly audit after several skills were added or renamed, producing a markdown report with high/medium/low-confidence recommendations and a suggested action order. ## Quick Start Run the skills-audit skill to review all SKILL.md files under .agents/skills and report duplicates, stale entries, and broken cross-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 agent skill files for duplicates?

Inventory all SKILL.md files with find, extract each frontmatter description, then compare skills within the same domain for identical descriptions or heavily overlapping trigger keywords. Flag likely duplicates as merge or delete candidates in a report.

What should a SKILL.md description contain for routing?

A description should state the topic and scope, include a 'Use when' clause with concrete scenarios, and a 'Triggers on' clause listing code symbols and natural phrases. Skills with disable-model-invocation set to true do not need trigger clauses.

How often should I run a skills audit?

Run it weekly, or after any week where more than one skill was added or renamed. Frequent audits catch drift early before overlapping triggers and stale descriptions make the catalog hard to route.

How do I find broken cross-references between skills?

Scan all skill bodies with ripgrep for backtick-quoted skill names, then confirm each referenced name has a matching .agents/skills/<name>/SKILL.md directory. Broken references usually appear after renames and should be fixed in the same audit pass.

When should I not merge two overlapping skills?

Do not merge skills that cover distinct workflows even within one domain, such as migration files versus schema authoring. Also avoid folding large 200+ line skills into others, since merging forces everything to load together.