writing-skills

To validate SKILL.md structure, run a baseline RED test to observe failures, then write a minimal SKILL.md with required name and description frontmatter to fix those failures and re-run tests.

TDD for skill documentation applies RED-GREEN-REFACTOR cycles to SKILL.md creation, ensuring consistent structure and verifiable quality by testing for required frontmatter and optional resources like scripts, references, and assets.

You enforce high-quality Skill documentation by applying test-driven development principles to SKILL.md creation, verifying required frontmatter, organizing content, and linking optional resources through structured validation cycles.

Yes, you can validate optional scripts, references, and assets in SKILL.md by running test cycles that support optional resources when present, alongside verifying required frontmatter fields like name and description.

You expose structured metadata for Skill discovery tooling by validating SKILL.md content that includes dependencies, components, and toxicity information, ensuring frontmatter contains name and description for proper indexing.

The best way to start writing a SKILL.md file is running a baseline RED test to observe failures, then writing minimal content with required name and description frontmatter to fix those failures before refactoring.