skill-format-universal

You can validate SKILL.md files by running a bash script that checks frontmatter, required body sections, and naming conventions. This enforces documentation standards and flags prohibited headings or placeholder text like TODO.

Required documentation sections include Scope, References, Rules, Instructions, Workflow, Examples, and Verification. Checking for these sections ensures canonical format adherence and discoverability across the skill ecosystem.

Format validation detects prohibited headings like "When to use" and flags placeholder text such as TODO or TBD. This content auditing prevents incomplete documentation from passing structural checks.

You can automate markdown consistency checks by running the validation script across all skills in the .claude/skills directory. The script performs structural and content checks on every SKILL.md file found.

The best way to enforce naming conventions is using an automated validation script that checks file structure and frontmatter against canonical standards, ensuring all skill files adhere to established naming rules.