- Home
- Skills
- Petekp
- Claude Code Setup
- Skill Auditor
skill-auditor_skill
- Shell
17
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill petekp/claude-code-setup --skill skill-auditor- SKILL.md7.1 KB
Overview
This skill audits an existing skill ecosystem and delivers actionable recommendations to improve agent-friendliness, consistency, and maintainability. It inventories global and project-level skills, evaluates individual skill quality, and produces a prioritized report with remediation steps. Use it to get a clear health score and concrete fixes for immediate wins.
How this skill works
The auditor scans skill directories to build an inventory, extracts metadata and size metrics, and detects supporting files like references, scripts, and assets. It runs per-skill checks on metadata quality, content length, progressive disclosure, actionability, and output contracts. Finally, it analyzes the collection for coverage gaps, overlaps, naming consistency, and organizational issues, and generates a prioritized report with grades and remediation steps.
When to use it
- After adding several new skills to check for overlap and consistency
- Quarterly or before major releases to maintain ecosystem health
- When skills feel ineffective or produce inconsistent outputs
- Before sharing or publishing a skill collection to external users
- When you need a prioritized list of concrete improvements
Best practices
- Keep skill descriptions concise and include clear "use when" triggers
- Split long content into reference files and keep manifests short
- Define explicit output contracts so related skills interoperate
- Use consistent naming and trigger patterns across similar skills
- Script repeatable operations to reduce manual steps and drift
Example use cases
- Audit a mixed set of global and project-scoped skills to find duplication
- Generate a health report with grades and a prioritized remediation plan
- Identify skills that are too long and recommend moving details to references
- Standardize trigger phrases and output formats across a domain
- Detect missing automation and recommend scripts for common tasks
FAQ
A quick inventory can complete in minutes; a full audit with per-skill grading and a written report typically takes longer depending on the number of skills, often under an hour for small collections and a few hours for large ones.
Will the auditor change my files?
No—audits are read-only. The output is a report with actionable recommendations; you apply changes manually or via separate automation.