Agent skill · Security

skills-audit

Audit .agents/skills SKILL.md files. Use for recurring checks of duplicate, overlapping, stale, inconsistent, or broken skills and merge/delete candidates.

LobeHub80,937★ · +310/wk · 1 repos on radarProfile →
claude-codeNOASSERTION
Install
npx skills add lobehub/lobehub --skill skills-audit --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 6 KB
Bundled scripts: none
Path: .agents/skills/skills-audit/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 81,252 · +315 this week
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Skills Audit Periodic review of the project-local skill set under `.agents/skills/`. The goal is to catch drift before the catalog becomes confusing — too many skills, overlapping triggers, descriptions that no longer match the body, references to skills that were renamed/deleted. **Recommended cadence:** weekly, or after any week where >1 skill was added/renamed. ## Procedure ### 1 — Inventory Build a fresh census of all SKILL.md files. Do NOT trust any prior cached list. ```bash find -L .agents/skills -name SKILL.md | wc -l # total count, including symlinked skills find -L .agents/skills -name SKILL.md -exec wc -l {} \; | sort -rn # by body length, including symlinked skills ``` Group by domain in a mental table (DB / state / UI / agent / testing / workflow / docs / etc.). Note new arrivals since last audit (`git log --since="1 week ago" -- .agents/skills/`). ### 2 — Pull frontmatter for all skills ```bash # Extract name + description for each SKILL.md for f in .agents/skills/*/SKILL.md; do echo "=== $(basename $(dirname $f)) ===" awk '/^---$/{c++; next} c==1' "$f" | head -20 done ``` Read the description block of every skill. The body can stay unread unless step 4 flags it. ##

What's inside
Steps it walks through
  1. Procedure
  2. 1 — Inventory
  3. 2 — Pull frontmatter for all skills
  4. 3 — Detect overlap / redundancy
  5. 4 — Description format consistency
  6. 5 — Stale-skill check
  7. 6 — Cross-reference integrity
  8. 7 — Output report
  9. Output rules
  10. What NOT to do
  11. Related history
Ships with 1 file
  • agents/openai.yaml
Commands it runs
find -L .agents/skills -name SKILL.md | wc -l                      # total count, including symlinked skills
find -L .agents/skills -name SKILL.md -exec wc -l {} \; | sort -rn # by body length, including symlinked skills
Extract name + description for each SKILL.md
for f in .agents/skills/*/SKILL.md; do
echo "=== $(basename $(dirname $f)) ==="
awk '/^---$/{c++; next} c==1' "$f" | head -20
done
Confirm the referenced code surface still exists
rg -l "response-compliance|openresponses" packages/ src/              # adjust per skill
git log --since="3 months ago" -- .agents/skills/ < skill > /SKILL.md # is it being maintained?
More from lobehub
All skills →
About this skill
What does the skills-audit skill do?

Audit .agents/skills SKILL.md files. Use for recurring checks of duplicate, overlapping, stale, inconsistent, or broken skills and merge/delete candidates.

How do I install it?

Run `npx skills add lobehub/lobehub --skill skills-audit --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 lobehub/lobehub, a repository with 81,252 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.

Keep going