writing-skills

To validate SKILL.md frontmatter and structure, automate checks that ensure the name field matches the folder name and the description includes WHAT, WHEN, and triggers. This enforces naming constraints, consistent triggers, and accurate metadata population for skill quality and discoverability.

Creating high-quality skill documentation requires following Anthropic best practices and repository conventions. You guide the creation and editing of SKILL.md files by enforcing YAML frontmatter presence, proper structure, described constraints, and consistent triggers for quality and discoverability.

Porting skills from other sources while maintaining quality involves auditing existing files to ensure the name matches the folder and the description includes WHAT, WHEN, and triggers. This validates dependencies, components, and overall structure consistency during the migration process.

You need skill linting for documentation validation when creating new skills, editing existing ones, or auditing quality and consistency. It applies when adding or modifying files under the skills directory, ensuring metadata like dependencies and components is accurately populated.

Skill validation works with both existing files and new skill creation. It applies when creating new skills, editing existing skills, porting from other sources, or reviewing skill quality, ensuring frontmatter presence, proper structure, and accurate metadata population across all scenarios.

Skill descriptions fail quality and consistency audits when they lack the required WHAT, WHEN, and triggers components, or when the name field does not match the folder name. Validation enforces these constraints to ensure proper structure and discoverability.