hermes-agent-skill-authoring

Validate in-repo SKILL.md frontmatter and structure for skill discovery.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/matthew-johnson/hermes-agent --skill hermes-agent-skill-authoring-matthew-johnson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hermes-agent-skill-authoring
Source: https://github.com/matthew-johnson/hermes-agent/tree/main/skills/software-development/hermes-agent-skill-authoring
Command: npx skills add https://github.com/matthew-johnson/hermes-agent --skill hermes-agent-skill-authoring-matthew-johnson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill defines and validates in-repo skill definitions by enforcing consistent frontmatter, required fields, and a predictable structure, enabling reliable discovery and onboarding.

Core Features & Use Cases

  • Enforces frontmatter requirements (name, description, version, author, license, metadata).
  • Documents the recommended in-repo skill layout (Overview, When to Use, Pitfalls, Verification).
  • Provides a guided workflow for creating, patching, or extending in-repo skills with validated templates.

Quick Start

Create or edit the in-repo SKILL.md under skills/<category>/<name>/SKILL.md following the frontmatter rules.

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 create an in-repo SKILL.md file with proper frontmatter validation?

Validate in-repo SKILL.md files by placing them under skills/<category>/<name>/SKILL.md with required frontmatter fields including name, description, version, author, license, and metadata. The skill manager tool enforces these rules during discovery.

What frontmatter fields are required for an in-repo skill definition?

Required frontmatter fields for in-repo skills are name, description, version, author, license, and metadata. The validation process verifies these fields exist, ensures body content is non-empty, and checks that size limits are respected.

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

The recommended in-repo SKILL.md structure includes Overview, When to Use, Pitfalls, and Verification sections. This predictable format ensures reliable skill discovery and onboarding through consistent documentation.

Where should in-repo skill files be located for the skill manager to discover them?

In-repo skill files must be placed at skills/<category>/<name>/SKILL.md for the skill manager tool to discover them. This directory convention ensures reliable discovery and validated reuse across repositories.

What happens if my SKILL.md body content is empty or exceeds size limits?

If SKILL.md body content is empty or exceeds size limits, validation fails. The skill manager enforces non-empty body content and size limit compliance before allowing skill discovery and reuse.

Can I extend or patch an existing in-repo skill definition?

You can extend or patch existing in-repo skills through a guided workflow with validated templates. The authoring process supports creating, patching, and extending skill definitions while maintaining frontmatter validation and standardized structure.