hermes-agent-skill-authoring

Automate SKILL.md frontmatter authoring and validation for in-repo skills under skills/.

13|3|Updated May 12, 2026
One-click install
npx skills add https://github.com/kevinnft/ai-agent-skills --skill hermes-agent-skill-authoring-kevinnft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hermes-agent-skill-authoring
Source: https://github.com/kevinnft/ai-agent-skills/tree/main/skills/software-development/hermes-agent-skill-authoring
Command: npx skills add https://github.com/kevinnft/ai-agent-skills --skill hermes-agent-skill-authoring-kevinnft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates authoring and validation of in-repo SKILL.md frontmatter and structure.

Core Features & Use Cases

  • Enforces a consistent in-repo SKILL.md layout, including mandatory fields like name and description, version, author, license, and hermes metadata.
  • Provides a clear peer-aligned structure and a validator workflow to ensure frontmatter validity and non-empty body content across skills located under skills/.
  • Guides teams through a repeatable editing and review process, from surveying peers to committing validated SKILL.md files.

Quick Start

Create or update the SKILL.md in skills/<category>/<skill-name>/SKILL.md with the required frontmatter and body, then run the validator to verify compliance.

Frequently Asked Questions about hermes-agent-skill-authoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate in-repo SKILL.md frontmatter fields?

To validate SKILL.md frontmatter, run the validator to check for required fields like name and description, enforce length limits, verify non-empty body content, and ensure peer-aligned schema compliance.

What is the required structure for an in-repo SKILL.md file?

The required SKILL.md structure includes mandatory frontmatter fields such as name, description, version, author, license, and hermes metadata, followed by a non-empty body documenting the skill.

How do I enforce consistent SKILL.md authoring across a team?

Enforce consistent SKILL.md authoring by applying a peer-aligned schema and validator workflow that checks mandatory frontmatter fields, length limits, and non-empty body content across all skills.

What frontmatter fields are mandatory for skills located under the skills/ directory?

Mandatory frontmatter fields for skills under skills/ include name and description at minimum, with additional peer-aligned metadata covering version, author, license, and hermes-specific schema.

Does the SKILL.md validator check for non-empty body content?

Yes, the SKILL.md validator checks for non-empty body content to ensure every skill file includes documented structure and substance beyond the frontmatter metadata block.

Can I use this validator for peer-aligned skill schemas in existing repositories?

Yes, you can use this validator for peer-aligned skill schemas by surveying existing peers, updating SKILL.md files to match required frontmatter and structure, then running validation before committing.