writing-skills

To write a SKILL.md for skill validation, create a file with valid frontmatter containing name and description fields, then add a structured body with overview, usage, quick start, and references sections.

Test-driven documentation for skill authoring is a structured approach that verifies reusable skills against frontmatter rules and CSO guidelines, ensuring techniques remain discoverable, testable, and compliant across projects.

Skill validation checks metadata fields like tagline, category, dependencies, and components against required standards, ensuring your SKILL.md frontmatter passes compliance and consistency checks before deployment.

No dependencies are required to start authoring skills. You only need to create a valid SKILL.md file with proper frontmatter, a well-structured body, and optional asset directories.

The best way to structure reusable skill documentation is following a template with overview, usage, quick start, and references sections, guided by test-driven principles to ensure consistency and verifiability.

Skill documentation fails frontmatter validation when the SKILL.md file omits required name and description fields or includes malformed metadata like invalid tagline, category, dependencies, or components entries.