hermes-agent-skill-authoring

Enforce standard SKILL.md structure with YAML frontmatter and validation rules.

78|16|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/sheawinkler/hermes-agent-ultra --skill hermes-agent-skill-authoring-sheawinkler
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hermes-agent-skill-authoring
Source: https://github.com/sheawinkler/hermes-agent-ultra/tree/main/skills/software-development/hermes-agent-skill-authoring
Command: npx skills add https://github.com/sheawinkler/hermes-agent-ultra --skill hermes-agent-skill-authoring-sheawinkler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating in-repo skills with consistent frontmatter, structure, and validation is error-prone without a standard guide. This skill provides a peer-approved template and workflow for shipping skills alongside Hermes-Agent.

Core Features & Use Cases

  • Enforces frontmatter requirements (name, description, version, author, license, metadata).
  • Documents recommended structure for in-repo SKILL.md (Overview, When to Use, Pitfalls, Verification Checklist, etc.).
  • Guides how to place supporting files under scripts/references/assets and how to commit.
  • Helps maintain consistency across skills in the software-development category.

Quick Start

Create an in-repo SKILL.md following the standard structure with a valid YAML frontmatter and the recommended sections.

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 with consistent YAML frontmatter and structure?▼

An in-repo skill requires a standard SKILL.md file with YAML frontmatter containing name and description fields, followed by a clear body with sections like Overview, When to Use, and Verification Checklist to ensure consistent metadata and actionable guidance.

What validation rules apply to skill frontmatter description fields?▼

Skill frontmatter validation enforces the presence of required name and description fields and enforces strict description length limits to maintain consistent metadata across in-repo skills within the repository.

Where should I place supporting scripts, references, and assets for an in-repo skill?▼

Supporting files for an in-repo skill should be placed in optional dedicated directories for scripts, references, and assets, keeping the repository structure organized alongside the main SKILL.md file.

What sections should be included in a SKILL.md body for software engineering workflows?▼

A SKILL.md body should include an Overview, When to Use, Pitfalls, and Verification Checklist to document recommended structure and provide actionable guidance for developers reading the skill.

Do I need external dependencies to ship in-repo skills with standard validation?▼

No external dependencies are required to ship in-repo skills; the skill provides a peer-approved template and workflow for enforcing frontmatter requirements and validation rules directly within the repository.