skill-audit-edho-ferdian

Audit a skills directory for staleness, redundancy, broken cross-references, and weak descriptions.

2|Updated Sep 6, 2026
One-click install
npx skills add https://github.com/edhoferdian/EEF --skill skill-audit-edho-ferdian-edhoferdian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-audit-edho-ferdian
Source: https://github.com/edhoferdian/EEF/tree/main/.agents/skills/skill-audit-edho-ferdian
Command: npx skills add https://github.com/edhoferdian/EEF --skill skill-audit-edho-ferdian-edhoferdian

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? As a collection of AI agent skills grows past a dozen interlinked entries, descriptions drift, cross-references break, and overlapping skills compete for the same triggers. This Skill runs a structured periodic audit across an entire skills directory so maintainers catch quality decay before it causes mis-triggering or dead-end instructions. ## Core Features & Use Cases - Four-category audit: Checks staleness (skills left behind as ecosystem conventions evolve), redundancy (unintentional trigger overlap without boundary statements), broken cross-references (pointers to missing files or skills), and description quality (too vague or too broad to trigger reliably). - Severity-ranked report: Produces a summary table plus per-skill findings with concrete evidence (file, line, or date), a clean list, and a prioritized recommendation list. - Strict scope control: Audits only the repository's own skills directory, explicitly excluding global agent harness installs, project memory, and unrelated folders. - Use Case: After adding a batch of new skills to your Claude Code ecosystem, run the audit to confirm no two skills claim the same trigger phrases and that every referenced file still exists. ## Quick Start Audit all skills in this repository's skills directory and report any staleness, redundancy, broken references, or description problems.

Frequently Asked Questions about skill-audit-edho-ferdian

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

FAQPage Schema
How do I audit a directory of Claude Code skills for quality problems?

Enumerate every SKILL.md under the skills directory, then run four checks in order: staleness via git log dates, broken cross-references via grep for referenced paths, redundancy via pairwise description comparison, and description quality via a read-through. Report findings with severity levels and evidence.

How to detect redundant or overlapping AI agent skills?

Extract each skill's description frontmatter and compare pairwise for shared trigger phrases and overlapping domain nouns. Flag a pair only when real overlap exists and neither skill states a boundary; intentional layering like lens-on-top relationships is not redundancy.

Does the skill audit modify or fix the skills it scans?

No. The audit only surfaces findings with concrete evidence such as files, lines, or dates. Fixes happen only as an explicit follow-up action when the user requests them, never folded into the audit itself.

What counts as a stale skill in a skill collection?

A skill is stale when it has not been substantively revisited in roughly 90 days while neighboring skills changed, or when its provenance section narrates facts that no longer hold, such as outdated skill counts or renamed files. Severity rises if other skills cross-reference it.

What are the limitations of this skill audit approach?

The audit covers only the repository's own skills directory, not global agent harness installs, project memory, or unrelated folders. It also cannot verify content accuracy of resolving paths; that falls under staleness judgment, not broken-reference detection.