argo-agent-skill-authoring

To create an in-repo SKILL.md file, you must include a YAML frontmatter block containing required name and description fields, followed by a non-empty body, ensuring it passes local validator compliance checks.

SKILL.md frontmatter validation requires a structured YAML header with mandatory name and description fields, adherence to size limits, and a non-empty body after the closing frontmatter delimiter for discoverability.

You validate SKILL.md files against repository conventions by running the local validator, which enforces YAML frontmatter rules, size limits, non-empty body requirements, and optional metadata blocks for peer-skill consistency.

Yes, you can include optional metadata blocks in an in-repo SKILL.md file to document lifecycle assets like references and scripts, provided the mandatory frontmatter and non-empty body requirements are met.

Your SKILL.md file fails validator compliance when it lacks the required YAML frontmatter fields (name and description), exceeds size limits, or contains an empty body after the closing frontmatter delimiter.

The best way to maintain consistency across multiple in-repo skills is applying a repeatable SKILL.md template with validated frontmatter and documented metadata conventions, promoting discoverability and maintainability across the repository.