Writing Skills

It treats skill writing as test-driven development for documentation: run a baseline test with a subagent to watch it fail without the skill, write the skill to fix that specific behavior, then verify compliance. The core insight is about Claude Search Optimization, where descriptions must contain triggering conditions, not workflow summaries, because testing showed Claude will follow the description and skip reading the actual skill content. Includes concrete structure templates, naming conventions, and a detailed breakdown of what makes skills discoverable. Assumes you already understand TDD fundamentals from the aegis skill. Most useful when you're actually creating or debugging skills that Claude isn't finding or following correctly.