write-skill

To enforce consistent markdown documentation and frontmatter, apply standardized SKILL.md conventions that require YAML frontmatter with name and description fields, ensuring uniform structure and discoverability across all files.

The required YAML frontmatter structure for skill documentation mandates a name and description field, while also supporting an optional last_verified field to track validation status across the repository.

To organize sections when writing a SKILL.md file, follow the mandated three-section structure: Purpose, Core Rules, and Detailed Sections, while applying gate patterns like Applicability and Monorepo Addendum to guide content organization.

You do not need any external dependencies to standardize your markdown templates, as the skill operates with zero dependencies to validate frontmatter and enforce section organization rules directly.

When authoring markdown documentation, avoid anti-patterns by ensuring you do not omit required frontmatter fields, deviate from the defined section structure, or bypass gate patterns that maintain documentation consistency.