1- [ ] `name` follows naming rules (lowercase, hyphens, 1-64 chars)
 2- [ ] `name` matches parent directory name
 3- [ ] `name` uses gerund form when possible (`processing-pdfs`)
 4- [ ] `description` is third person ("Extracts...", not "I extract...")
 5- [ ] `description` includes what it does AND when to use it
 6- [ ] `description` has no markdown formatting
 7- [ ] `description` includes trigger keywords for discovery
 8- [ ] SKILL.md body is under 500 lines
 9- [ ] Additional details are in separate reference files
10- [ ] No time-sensitive information (or in "old patterns" section)
11- [ ] Consistent terminology throughout
12- [ ] Examples are concrete, not abstract
13- [ ] File references are one level deep from SKILL.md
14- [ ] Reference files >100 lines have table of contents
15- [ ] Progressive disclosure used appropriately
16- [ ] Workflows have clear steps
17
18## Scripts (if applicable)
19
20- [ ] Scripts are tested by actually running them (not just written)
21- [ ] Scripts solve problems rather than punt to agent
22- [ ] Error handling is explicit and helpful
23- [ ] No magic constants (all values justified/documented)
24- [ ] Required packages listed and verified as available
25- [ ] Scripts have clear documentation
26- [ ] No Windows-style paths (use forward slashes)
27- [ ] Validation/verification steps for critical operations
28- [ ] Feedback loops included for quality-critical tasks