Skill Audit

Audit a skill before calling it ready. Favor Tessl output, repo conventions, and the skill's actual file shape over taste.

Principles

• Evidence beats hunches
• Discovery matters: score name and description before polishing the body
• Keep SKILL.md lean; move depth into references/ or scripts only when they earn their keep
• Prefer the smallest change set that improves activation, clarity, or verification
• Audit only the requested scope; flag adjacent issues separately

Boundaries

• Do not expand an audit into unrelated repo documentation, product/runtime verification, or general code review.
• Report an out-of-scope gap as a capability and required next step. Do not add cross-package invocation, routing, or requirements to the audited package.

Before You Start