writing-skills

To write a SKILL.md using test-driven development, apply a red-green-refactor cycle to structure documentation, identify failure scenarios, and validate skill effectiveness before deployment. This enforces concise specifications with required YAML frontmatter for name and description.

Test-driven development for skill documentation is a structured method to craft, edit, and validate reusable skills. It identifies failure scenarios and rationalization excuses, setting red lines to ensure skill effectiveness and quality assurance before deployment.

Validate skill effectiveness before deployment by running a TDD-inspired consistency check on your SKILL.md. This process ensures the specification is concise, tests failure scenarios, and verifies that references, scripts, and assets function correctly.

Yes, YAML frontmatter is required to create a new skill. Your SKILL.md must include a name and description in the frontmatter to enforce a concise, description-focused specification before adding optional references, scripts, or assets.

The best way to structure reusable skill documentation is separating references, scripts, and assets from the core SKILL.md. This keeps the specification concise and description-focused while maintaining extensibility for testing and validation workflows.