skill-creator

Invoke the skill creator by saying create a skill or turn this into a skill. It produces a SKILL.md with YAML frontmatter containing name, description, and trigger phrases, plus a tight instruction body following Hermes best-practice structure.

A SKILL.md needs YAML frontmatter with at least a name and description including one clear trigger phrase, followed by a concise Markdown instruction body. Heavy content belongs in references, templates, scripts, or assets directories loaded only on demand.

Before writing, check if an existing skill covers 80% or more of the need and expand it instead of creating a duplicate. Overlapping skills should be merged, shared logic moved into referenced files, and stale skills trimmed or quarantined.

The description is loaded into the system prompt on every turn for skill discovery, so long descriptions bloat token usage continuously. Keep descriptions concise with one trigger phrase and put detailed content in the body or linked files.

Defer creating a skill when the request is a one-off task that will not recur. Also avoid creating one when an existing skill already covers the need, since skill bloat reduces token efficiency across every session.