writing-skills

Skill documentation requires YAML frontmatter containing name and description fields to standardize discovery. Authors enforce this concise frontmatter-driven structure to ensure reliable, easily discoverable skills across platforms.

Test-driven development for skill authoring applies the RED-GREEN-REFACTOR cycle to verify skill behavior before deployment. This iterative testing workflow ensures bulletproof quality and validates documentation patterns rigorously.

Validate skill behavior by performing the RED-GREEN-REFACTOR testing cycle after writing the skill body. This test-driven workflow verifies functionality iteratively, ensuring bulletproof quality and reliable documentation before deployment.

Progressive disclosure patterns keep skill bodies concise while loading heavy references on demand. This structure supports discoverability and consistency without overwhelming users with extensive documentation upfront.

Rationalization tracking monitors decision-making patterns within skill documentation to identify red flags and maintain bulletproof quality. It provides cross-skill references and best-practice guidelines for consistent authoring.

Frontmatter with name and description is required to create a skill. The body alone is insufficient because frontmatter standardizes discovery and enables the test-driven validation workflow to function properly.