A skill is executable procedure, not just a prompt. Treat origin, requirements, permissions, and change history as part of the artifact.
Direct answer
Install only after you can explain what the skill reads, writes, calls, and asks the agent to remember.
01 / Discover
List and open the skill
Use the Skills System, a GitHub tap, ClawHub, a direct URL, or an external directory. Record the origin before copying anything.
02 / Inspect
Review source and requirements
Read SKILL.md, referenced files, commands, environment variables, network targets, and the tools the procedure expects.
03 / Install
Place it in a known scope
Hermes reads local skills from ~/.hermes/skills/. Prefer a narrow, reversible install before sharing it across machines.
04 / Test
Run one bounded task
Use the least-privileged environment that still exercises the workflow. Confirm both the expected output and the stop path.
05 / Approve
Review agent-authored changes
When write approval is enabled, proposed skill changes can remain staged under ~/.hermes/pending/skills/ before they become active.
06 / Share
Publish the evidence with the skill
Share the source, requirements, tested environment, and known limits—not just a Markdown file that happens to run.
SKILL.md anatomy
Readable procedure, explicit boundary
Hermes follows the Agent Skills-compatible SKILL.md pattern. Frontmatter makes the skill discoverable; the body should explain when to use it, what to inspect, which steps to follow, and where to stop.
---
name: review-repository-change
description: Inspect a proposed change before it is accepted.
---
1. Read the source and referenced files.
2. Identify permissions and external calls.
3. Test the smallest reversible case.
4. Stop when evidence is incomplete.