hermes-agent-skill-authoring

Validate YAML frontmatter and structure of in-repo SKILL.md files.

2|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/john-data-chen/hermes-agent-backup --skill hermes-agent-skill-authoring-john-data-chen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hermes-agent-skill-authoring
Source: https://github.com/john-data-chen/hermes-agent-backup/tree/main/skills/software-development/hermes-agent-skill-authoring
Command: npx skills add https://github.com/john-data-chen/hermes-agent-backup --skill hermes-agent-skill-authoring-john-data-chen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes and enforces a consistent frontmatter-driven template for in-repo skills, ensuring every skill meets a standard discovery surface and validation path.

Core Features & Use Cases

  • Documents the two skill-placement options (user-local and in-repo) and explains when to use each.
  • Outlines required frontmatter fields and the validator workflow to verify structure.
  • Provides a peer-aligned pattern for subsequent in-repo skills, reducing onboarding time and ensuring consistency.

Quick Start

Create or update an in-repo SKILL.md at skills/<category>/<skill-name>/SKILL.md following the documented frontmatter, structure, and validator.

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 SKILL.md frontmatter for in-repo skills?

To validate SKILL.md frontmatter for in-repo skills, enforce the presence of required YAML fields like name and description, then rely on the project validator to check size and formatting rules.

What frontmatter fields are required when authoring a Hermes skill?

When authoring a Hermes skill, the required frontmatter fields are name and description. Optional metadata blocks include version, author, and license to ensure proper discoverability.

What is the correct file structure for in-repo skill authoring?

The correct file structure for in-repo skill authoring places your SKILL.md file at skills/<category>/<skill-name>/SKILL.md, ensuring consistent layout and metadata validation across the repository.

When should I use in-repo skills instead of user-local skills?

You should use in-repo skills when you need project-level discovery and peer-aligned consistency, whereas user-local skills suit individual workflows outside the repository validation path.

Why does my in-repo skill fail structure validation?

In-repo skill structure validation fails when the SKILL.md file omits required YAML frontmatter fields or violates project validator size and formatting constraints enforced during the authoring workflow.