Creating Skills

It walks through the full structure: YAML frontmatter rules, how to write descriptions that Claude will actually find when searching ("Use when tests have race conditions" beats "For async testing"), and why gerund names work better. The degrees of freedom section is smart: be prescriptive for fragile operations, give principles for creative ones. Includes real examples of good versus bad code samples, token budgets for different skill types, and compression techniques to keep skills under 500 lines. Basically codifies what makes a skill discoverable and scannable instead of just another markdown file that gets ignored.