hermes-agent-skill-authoring

To author in-repo skills, create a SKILL.md file under skills/<category>/<skill-name>/ with YAML frontmatter containing name and description, plus a non-empty Markdown body. This standardizes discovery and validation across repositories.

Hermes-Agent skill validation requires YAML frontmatter containing name and description fields. Optional metadata and category alignment are also enforced by validators to ensure peer consistency and quality control.

Yes, the Hermes-Agent skill authoring format works for version control because in-repo skills are defined as SKILL.md files. They can be versioned and reviewed alongside code, promoting collaboration and quality control.

The best way to structure in-repo skill documentation is using a non-empty Markdown body with structured sections. Guide authors to provide overview, application contexts, and practical usage scenarios for ship-ready documentation.

In-repo skill frontmatter validation fails when required fields like name and description are missing. Validators also enforce optional metadata and category alignment to support peer consistency and quality control.

No, Hermes-Agent skills must be defined using a SKILL.md file located specifically under skills/<category>/<skill-name>/. This directory structure enables standardized discovery and automated validation within the ecosystem.