hermes-agent-skill-authoring

Define in-repo SKILL.md files with YAML frontmatter and validator-enforced structure.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill defines how to author in-repo SKILL.md files with frontmatter and a validation front-end, ensuring consistent discovery and loading across teams. The frontmatter enforces required fields like name and description, while the body provides actionable instructions for structuring, validation, and maintenance.

Core Features & Use Cases

  • Establishes a standard SKILL.md frontmatter with required fields (name, description) and optional metadata to guide discovery and tooling.
  • Documents the recommended directory layout (scripts/, references/, assets/) and how the skill loader uses them at runtime.
  • Provides guidelines for validating in-repo skills with the repository's skill validator to maintain peer consistency.

Quick Start

Create or update an in-repo SKILL.md under skills/software-development/hermes-agent-skill-authoring so it starts with a YAML frontmatter containing name and description and adheres to the repository 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 write a SKILL.md file with YAML frontmatter for in-repo skills?

In-repo skills require a SKILL.md file with a YAML frontmatter block containing the required name and description fields, followed by a structured body that provides actionable instructions for the skill loader.

What is the recommended directory layout for maintaining in-repo skills?

The recommended directory layout for in-repo skills organizes runtime components into separate directories, specifically using scripts/ for executable logic, references/ for supporting documentation, and assets/ for static files.

How do I validate in-repo skills to ensure consistent metadata and structure?

You validate in-repo skills by running the repository's skill validator against your SKILL.md files to enforce required YAML frontmatter fields and ensure consistent metadata, structure, and peer discoverability.

What fields are required in SKILL.md frontmatter for skill discovery and loading?

The required fields in SKILL.md frontmatter are name and description, which are enforced by the validation front-end to guarantee consistent discovery and loading across teams.

Can I use optional metadata in SKILL.md frontmatter alongside required fields?

Yes, you can include optional metadata in the YAML frontmatter alongside the required name and description fields to provide additional context that guides tooling and skill discovery.

When do I need to use a validation front-end for in-repo skills?

You need a validation front-end for in-repo skills when maintaining skills under directories like skills/software-development/ to ensure every SKILL.md file meets repository standards for metadata and structure before loading.