Use when reviewing, grading, auditing, or improving a whole existing skill or pack - judging whether a skill is good, fixing one that misfires or won’t activate, or driving one or many skills to a quality bar. Audits to an absolute A+ bar and hands back ship-ready SKILL.md rewrites, not a report the user must act on. Do NOT use when tightening only a description or trigger in isolation - use skill-description-writer instead; do NOT use when authoring a brand-new skill from scratch - use skill-creator instead.
Click to play with sound.
---
name: Skill Auditor
description: Use when reviewing, grading, auditing, or improving a whole existing skill or pack - judging whether a skill is good, fixing one that misfires or won't activate, or driving one or many skills to a quality bar. Audits to an absolute A+ bar and hands back ship-ready SKILL.md rewrites, not a report the user must act on. Do NOT use when tightening only a description or trigger in isolation - use skill-description-writer instead; do NOT use when authoring a brand-new skill from scratch - use skill-creator instead.
---
# Skill Auditor
Audit whole skills and packs to an absolute A+ bar and hand back ship-ready rewrites - not a report the user then has to act on. Where an artifact falls short, diagnose precisely and return the finished, committable SKILL.md.
## The bar - what A+ means
A+ is absolute, not the top of whatever is in front of you. A skill is A+ only if all of these hold:
- It **fires on exactly the right requests and never on the wrong ones.** The description front-loads a concrete trigger a router can act on with no ambiguity, and carves negative scope against every plausible neighbor.
- It **does not collide** with any other skill. Two skills never both fire for one request unless that is intended and their bodies coordinate.
- Its body carries the **full paid-quality anatomy** (skill-author is the canonical standard): an ordered operating procedure, input elicitation, concrete practitioner thresholds, at least one worked artifact (filled example, good/bad pair, FILL-field template, or runnable calculator), an explicit deliverable, a Do NOT section with the why, and a quality bar. A body of tips-in-arbitrary-order is a B at best, however accurate the tips.
- It is **token-disciplined.** Descriptions load every session; bodies load on trigger. Every word is paid for on every session of every installer. Bloat is a recurring tax.
- It is **correct and self-contained** - real tools, paths, and numbers; no hallucinated capabilities; no context it has not established; no dates, versions, or "latest".
If an expert author could meaningfully improve it, it is not yet A+.
## Procedure
Read every artifact from source - the actual SKILL.md, or pull from the catalog via browse_skills / browse_packs. Audit what ships, not what you assume ships.
… install to load the full skill