savarez-agent-skill-authoring

To validate in-repo skill definitions, enforce required frontmatter fields like name and description, and apply a peer-matched outline to ensure standardized documentation across the repository.

Required frontmatter fields for authoring SKILL.md files include name and description, ensuring your YAML structure meets presence and description length limits for repository consistency.

The best way to standardize skill documentation is to apply a peer-aligned structure and validator-driven process, enforcing frontmatter presence, naming conventions, and standardized outlines across all skills.

Set up a standardized outline for skills-management by following in-repo skill-writing guidelines that define a peer-matched structure, guiding creation and updates for software-development skills.

Yes, skill authoring enforces description length limits within the YAML frontmatter to maintain consistency and discoverability, requiring validation to ensure compliance before repository integration.

In-repo skill validation fails when SKILL.md files lack required frontmatter fields, violate YAML structure rules, exceed description length limits, or miss the standardized peer-matched outline.