hermes-agent-skill-authoring

Create and validate in-repo SKILL.md frontmatter and structure for Hermes skills.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide helps contributors author in-repo SKILL.md files that comply with Hermes Skill conventions, ensuring consistent frontmatter and structured documentation.

Core Features & Use Cases

  • Enforces the required frontmatter (name, description) and a peer-aligned YAML header, plus supported metadata fields.
  • Provides a standard in-repo skeleton and workflow for validating, organizing, and placing skills under skills/<category>/<name>.
  • Guides editors through size constraints, optional resource directories (scripts, references, assets), and a predictable documentation layout.

Quick Start

Write the in-repo SKILL.md following the standard frontmatter and structure, and validate it with the skill tool.

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?

Validate SKILL.md frontmatter by enforcing required name and description fields, checking size limits, and verifying a peer-aligned YAML header structure against Hermes Skill authoring conventions.

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

The required SKILL.md structure includes a peer-aligned YAML header with supported metadata fields, standard documentation layout, and placement under the skills/<category>/<name> directory path to ensure organizational consistency.

Do I need a specific directory structure to author Hermes skills?

Yes, authoring Hermes skills requires placing files under a skills/<category>/<name> directory structure, which allows optional resource directories for scripts, references, and assets to maintain predictable organization.

What are the size limits and constraints for in-repo skill documentation?

In-repo skill documentation enforces specific size limits on SKILL.md files and supports optional resource directories for scripts, references, and assets to keep documentation structured and within peer-aligned guidelines.

Can I include optional resource directories when creating in-repo skills?

Yes, you can include optional resource directories for scripts, references, and assets alongside your SKILL.md file, maintaining a predictable documentation layout within the skills/<category>/<name> path.

What's the best way to organize in-repo skills across a development team?

The best way to organize in-repo skills is following the standard skeleton structure, validating frontmatter with the skill tool, and placing files under skills/<category>/<name> to ensure consistency across peer contributors.