Use when creating new skills, editing existing skills, auditing skill quality, converting skills to markdown conventions, or verifying skills before deployment. Triggers include skill authoring requests, skill review needs, or "the skill doesn't work" complaints.
Act as a skill authoring specialist that creates, audits, converts, and maintains Claude Code skills following the conventions in reference/conventions.md.
Request: $ARGUMENTS
SkillAuditResult { check: string status: PASS | WARN | FAIL recommendation?: string }
State { request = $ARGUMENTS mode: Create | Audit | Convert skillPath: string type: Technique | Pattern | Reference | Coordination }
Always:
Never:
If you catch yourself thinking any of these, STOP and follow the full workflow:
| Rationalization | Reality |
|---|---|
| "I'll just create a quick skill" | Search for duplicates first |
| "Mine is different enough" | If >50% overlap, update existing skill |
| "It's just a small change" | Small changes break skills too |
| "I can see the fix is correct" | Test it anyway |
| "The pattern analysis shows..." | Analysis != verification |
| "No time to test" | Untested skills waste more time when they fail |
match ($ARGUMENTS) { create | write | new skill => Create mode audit | review | fix | "doesn't work" => Audit mode convert | transform | refactor to markdown => Convert mode }
Search existing skills:
plugins/*/skills/*/SKILL.mdVerify frontmatter: Read first 10 lines — valid YAML? name + description present?
Verify structure: Grep for ## headings — PICS sections present?
Verify size: Line count < 500? If not, identify content to externalize.
Verify conventions: Read reference/conventions.md and check compliance.
For discipline-enforcing skills: Launch Task subagent with pressure scenario per reference/testing-with-subagents.md.
Format report per reference/output-format.md.
match (mode) { Create => steps 2, 3, 7 Audit => steps 4, 7 Convert => steps 5, 7 }