Table of Contents
- What the Skills Hub actually is
- What's inside the Hermes Skills Hub in 2026
- How installing actually works
- The security paragraph you should actually read
- Hermes writes its own skills too
- Writing your own Hermes agent skills
- The directories worth bookmarking
- Do Claude Code and OpenClaw skills work in Hermes?
- Skills vs MCP servers
- Skills only pay off on an always-on agent
- Hermes Skills Hub FAQ
- Is the Hermes Skills Hub free?
- How many skills are in the Hermes Skills Hub?
- Can the agent install hub skills by itself?
- How do I publish my own skill?
- Why isn't my installed skill firing?
hermes skills CLI or straight from chat with /skills. We host Hermes agents for a living at Agent37, so we work inside this ecosystem every day. This guide covers what the hub actually contains right now, how installs and security scanning really work, and the parts every other write-up glosses over.What the Skills Hub actually is
hermes skills CLI, and the /skills command in chat. This guide is about that second, real one.~/.hermes/skills/, the directory that is the single source of truth. It joins the agent's skill index, a compact list that costs about 3,000 tokens at session start, with full content loaded only on demand. And it becomes a slash command, so /gif-search funny cats works in the CLI and in any connected chat platform. You can even stack up to five: /github-pr-workflow /test-driven-development fix issue #123 and open a PR loads both skills in order.What's inside the Hermes Skills Hub in 2026
Slice | Count |
Built-in skills | 82 |
Official optional skills | 117 |
Community skills | 90,501 |
Registries | 11 |
Categories | 199 |
Total skills | 90,700 |
hermes skills install official/<category>/<skill>. The heavier tooling lives there (MLOps alone has 31 entries), including openclaw-migration, which imports an existing OpenClaw setup into Hermes, memories and skills included.How installing actually works
hermes skills search kubernetes
hermes skills inspect openai/skills/k8s
hermes skills install openai/skills/k8s
hermes skills install official/security/1password
hermes skills install https://example.com/SKILL.md --name my-skill
hermes skills update
hermes skills uninstall k8s/skills search, /skills install, and so on), which matters more than it sounds. You can install a skill from your phone, mid-conversation in Telegram or WhatsApp, and the agent picks it up in its next session. Use /reset when you want it active immediately.hermes skills audit re-scans everything you have installed whenever you ask.--force flag can override caution-level findings. It cannot override a dangerous verdict. That hard stop exists for good reason.required_environment_variables reads secrets from ~/.hermes/.env, and required_credential_files handles OAuth and service-account files. Keys stay on your machine, never inside the skill folder, and hermes skills inspect shows what a skill will ask for before you commit.The security paragraph you should actually read
hermes skills inspect before you install; a skill is a markdown file, and you can just read it. Read any bundled scripts folder with the same eyes: helper scripts are code the agent may run, not documentation. And leave --force alone unless you have read the finding it is overriding.Hermes writes its own skills too
skill_manage tool, which the docs call the agent's procedural memory, and it improves those skills during use. Since v0.18.0 there is also /learn: point it at a URL, a directory, or the workflow you just walked it through, and it distills a reusable skill on the spot.skills.write_approval) stages every agent-authored change under ~/.hermes/pending/skills/ for human review with /skills approve; it ships disabled, so turn it on if a self-editing agent makes you nervous. And the bundled-skill sync never stomps your work: edit any shipped skill and updates skip it from then on, with hermes skills reset <name> --restore as the undo. A built-in Curator watches usage on top of that, surfacing unmanaged skills and flagging ones you never invoke.Writing your own Hermes agent skills
~/.hermes/skills/ and it is live at the next session. The rule that trips everyone: the agent decides whether to load a skill by matching your request against the frontmatter description field, not the body. Write the description as a trigger condition ("Use when the user asks about invoices or billing exports"), or your perfectly good skill never fires.hermes chat --toolsets skills -q "your trigger phrase" shows whether the skill loads. When it holds up, publish it with hermes skills publish (the FAQ below has the exact command) or share it with your team as a tap.The directories worth bookmarking
- awesome-hermes-agent (by 0xNyk): the most-starred independent directory, about 250 entries with production/beta/experimental maturity tags, 5,400+ stars, updated a few times a month. Plainly states it is not an official Nous Research project.
- awesome-hermes-skills (by ZeroPointRepo): the longer list at 350+ entries, but about 200 of those just catalog the built-in and optional skills that already ship with Hermes. The roughly 170 community projects are the part tagged by maturity, each linking out to per-project install instructions. Updated almost daily. Run by the TranscriptAPI team, with the affiliation disclosed.
- Hermes Atlas (hermesatlas.com): 240 ecosystem repos ranked by live GitHub star counts. The number one skill pack, obra/superpowers, sits at 277,000+ stars.
hermes skills tap add <owner/repo> at any GitHub repo full of SKILL.md folders and it becomes a private registry. No server, no sign-up, no release pipeline. Set a GITHUB_TOKEN in your environment or the hub runs into GitHub's 60-requests-per-hour anonymous ceiling; with a token it is 5,000.Do Claude Code and OpenClaw skills work in Hermes?
metadata.openclaw dependency gating, Hermes's own metadata.hermes.* toolset wiring. Agents ignore foreign metadata instead of erroring on it, so a Claude Code skill generally just works, minus the Claude-specific behavior. For a full switch, the optional openclaw-migration skill and hermes claw migrate bring an OpenClaw setup across wholesale, and imported user skills land in ~/.hermes/skills/openclaw-imports/. Already keep a folder of Claude Code skills? Point skills.external_dirs at it (say, ~/.claude/skills) and Hermes indexes those skills in place, no reinstall needed.Skills vs MCP servers
config.yaml, let Hermes work out a reliable call sequence, then run /learn and it distills that sequence into a skill it can repeat. Our MCP vs Claude Skills guide maps the distinction across the wider agent ecosystem.Skills only pay off on an always-on agent
hermes skills CLI workflows in this guide need a machine you control.hermes skills commands in this guide. Building a product on agents instead? The Agent37 Cloud API provisions persistent Hermes instances from $1.99/mo behind a single API call. One honest caveat either way: at these prices support is an AI bot first, not a human help desk.Hermes Skills Hub FAQ
Is the Hermes Skills Hub free?
How many skills are in the Hermes Skills Hub?
Can the agent install hub skills by itself?
/skills commands. The agent writes and edits its own skills through skill_manage, but it does not shop the hub autonomously.How do I publish my own skill?
hermes skills publish skills/my-skill --to github --repo owner/repo, then anyone can add that repo as a tap. Getting into the trusted tier requires a Hermes core pull request; community trust is the default for everything else.Why isn't my installed skill firing?
description is the problem. The agent matches your request against each skill's description field, not its body, so a vague description never triggers. Rewrite it as a condition ("Use when..."), then restart the session or run /reset so the refreshed index picks it up.