hermes-agent-skill-authoringlisted
Install: claude install-skill ykoh42/async-hermes-agent
# Authoring Hermes-Agent Skills (in-repo)
## Overview
There are two places a SKILL.md can live:
1. **User-local:** `~/.hermes/skills/<maybe-category>/<name>/SKILL.md` — personal, not shared. Created via `skill_manage(action='create')`.
2. **In-repo (this skill is about this case):** `skills/<category>/<name>/SKILL.md` from the repository root — committed and shipped with the source. Use `write_file` + `git add`. `skill_manage(action='create')` does NOT target this tree.
## When to Use
- User asks you to add a skill "in this branch / repo / commit"
- You're committing a reusable workflow that should ship with hermes-agent
- You're editing an existing skill under `skills/` (use `patch` for small edits and `write_file` for rewrites; `skill_manage` can edit it only when that tree is configured as an external skills directory)
## Required Frontmatter
Source of truth: `tools/skill_manager_tool.py::_validate_frontmatter`. Hard requirements:
- Starts with `---` as the first bytes (no leading blank line).
- Closes with `\n---\n` before the body.
- Parses as a YAML mapping.
- `name` field present.
- `description` field present, ≤ **1024 chars** (`MAX_DESCRIPTION_LENGTH`).
**Long descriptions are truncated to 57 chars + "..." in the system
prompt skill index** (`extract_skill_description` in `agent/skill_utils.py`);
longer text is visible via `skills_list()` and `skill_view()`.
Front-load the trigger phrase.
- Non-empty body after the closing `---`.
Peer-matched shape u