skill-auditor

<critical_workflow> MANDATORY: Read best practices FIRST, before auditing:

1. Read @shared/rules/CORE-PRINCIPLES.md for XML structure, conciseness, progressive disclosure
2. Read @shared/rules/ANTI-PATTERNS.md for common mistakes to detect
3. Read @shared/rules/XML-TAG-GUIDE.md for required/conditional tags and nesting rules
4. Handle edge cases:
   • If reference files are missing or unreadable, note in findings under "Configuration Issues"
   • If YAML frontmatter is malformed, flag as critical issue
   • If skill references external files that don't exist, flag as critical issue
   • If skill is <100 lines, note as "simple skill" and evaluate accordingly
5. Read the skill files (SKILL.md and any references/, workflows/, scripts/ subdirectories)
6. Evaluate against best practices from steps 1-3

Use ACTUAL patterns from shared rules, not memory. </critical_workflow>

<evaluation_areas>

• name: Lowercase-with-hyphens, max 64 chars, matches directory name, follows verb-noun convention
• description: Max 1024 chars, third person, includes BOTH what it does AND when to use it, no XML tags in description

<contextual_judgment> Apply judgment based on skill complexity:

Simple skills (single task, <100 lines):

• Required tags only is appropriate -- don't flag missing conditional tags
• Minimal examples acceptable
• Light validation sufficient

Complex skills (multi-step, external APIs, security concerns):

• Missing conditional tags (security_checklist, validation, error_handling) is a real issue
• Comprehensive examples expected
• Thorough validation required

Delegation skills (invoke subagents):

• Success criteria can focus on invocation success
• Pre-validation may be redundant if subagent validates