What is a Hermes skill, tool or plugin, and which do I need?
A Hermes skill is a set of written instructions that Hermes reads when it needs them. A tool is an action Hermes can actually run, such as a web search or a terminal command. A plugin is an add-on, usually Python code, that can bring new tools and other features. If a guide shows a capability your Hermes lacks, find out which of the three it needs. A skill can’t supply a tool that isn’t there, and installing a plugin doesn’t turn it on.
The three things, side by side
These descriptions follow Hermes Agent v0.23.1 (commit 3b42157, released 9 November 2026) and its official documentation.
| Skill | Tool (in a toolset) | Plugin | |
|---|---|---|---|
| What it is | A folder holding a SKILL.md file of instructions, sometimes with scripts and reference files |
A function the model can call, grouped into toolsets such as web or terminal |
Usually Python code with a plugin.yaml manifest or a pip package. Portable plugin packages can instead bundle skills and MCP servers |
| What it adds | Know-how: when to do something and which existing tools to use | The ability to act | New tools, slash commands, hooks, chat platforms, model providers or memory backends |
| Where it lives | ~/.hermes/skills/ |
Built into Hermes, or supplied by a plugin or an MCP server | ~/.hermes/plugins/, bundled with Hermes, or installed as a pip package |
| Off until you act? | Bundled skills are copied in at install. Hub skills install with hermes skills install |
Each toolset is switched on or off per chat platform | Yes. Most plugins stay disabled until you enable them |
| Brings its own credentials? | No | No | No |
Hermes’s developer guide gives the rule of thumb. Write a skill when the job can be done with instructions, shell commands and existing tools. Write a tool when the job needs its own integration, such as an API key or browser automation.
A skill gives Hermes instructions, not new abilities
Hermes keeps a short index of installed skills in its prompt. It loads a skill’s full text only when a task calls for it. Each skill also becomes a /skill-name command in chat.
A skill can include scripts, but Hermes runs them with the tools it already has, such as terminal. If those tools are switched off, the skill can’t run them. A skill can also declare that it needs a particular toolset, and Hermes hides it when that toolset is missing. So a “Gmail skill” teaches Hermes how to handle email. Your Hermes still needs a working route to Gmail before it can act.
Useful commands:
hermes skills list # what is installed
hermes skills search "<query>" # look in skill registries
hermes skills inspect <id> # read before installing
hermes skills install <id>
hermes skills config # turn individual skills on or off
There is no hermes skills enable command. Use hermes skills config to turn a skill on or off, overall or for one chat platform.
A tool is what Hermes can actually do
Tools are grouped into toolsets, and each chat platform has its own list. A toolset can be on in the terminal and off for Telegram. Check the platform you actually use:
hermes tools list --platform telegram
hermes tools enable <toolset> --platform telegram
An enabled tool can still be missing. When Hermes builds the list of tools it offers the model, it runs each tool’s availability check and leaves out any tool that fails. The model never sees that tool. The usual causes are a missing API key or a missing system dependency. hermes tools list shows whether each toolset is switched on or off in your settings. It doesn’t show whether the tools actually work. hermes doctor shows the cause: its Tool Availability section names the missing variable or reports a dependency that isn’t met.
MCP servers are a third way to add tools. You add a server with hermes mcp add (or under mcp_servers in config.yaml), and its tools appear as their own toolset. hermes mcp test <name> checks the connection. An MCP server adds tools, and by default it can also ask Hermes to make model calls on its behalf, using your model. A plugin can change much more.
A plugin is code you choose to enable
A plugin can register tools, commands, hooks, gateway platforms and backends such as image generation, memory or model providers. A plugin’s bundled skills are named plugin:skill.
Hermes’s plugin documentation says general plugins “are disabled by default”. Discovery lists them, but “nothing with hooks or tools loads until you add the plugin’s name to plugins.enabled”. Installing asks whether to enable the plugin now, and the default answer is no. Bundled platform plugins, bundled backends, memory providers, context engines and model providers are exceptions to this rule. Platforms you install yourself still need enabling.
hermes plugins search "<query>"
hermes plugins install <name>
hermes plugins list # shows enabled, disabled or not enabled
hermes plugins enable <name>
Check your version if a plugin install can’t find a new plugin. The v0.23.1 release notes say the published catalog grew past the 2 MiB size limit that older clients accepted. As a result, “every install silently fell back to the catalog it shipped with”. Newly added plugins couldn’t be found, older pinned versions were installed instead, and newer removals from the catalog were missed. That meant a plugin removed from the catalog could still be installed by name. v0.23.1 raises the limit to 16 MiB. Installs on v0.23.0 or older keep falling back until they update.
Diagnosing “the guide says Hermes can do this”
Work through these in order. After each change, retest with the same small task in a new session. Restart Hermes after installing a dependency.
- Is it a skill?
hermes skills listandhermes skills search. If it’s installed but ignored, checkhermes skills configfor the platform you use. - Is the toolset on for your platform?
hermes tools list --platform <platform>. - Is the tool on but unavailable?
hermes doctor. Add the missing key withhermes setupor in~/.hermes/.env, or install the missing dependency. - Is it a plugin?
hermes plugins list. “Not enabled” means installed but not loaded. If a search can’t find it on v0.23.0 or older, update first. - Is it an MCP server’s tool?
hermes mcp list, thenhermes mcp test <name>.
If you prefer a browser to the terminal, Hermes’s web dashboard documents a Skills page. It can toggle skills, show each toolset’s status and setup requirements, and install from the skill hub. The dashboard’s System page can also run doctor.
A finished task proves more than a successful install. Look for an actual tool call and its result, not just a confident reply. When the tool appears and runs but the model handles it badly, see why Hermes rejects a model or ignores its tools.
Credentials and trust come with every choice
Installing a skill or plugin never supplies an account or API key. A skill can declare the keys it needs, and Hermes asks for them only when the skill loads in the local CLI. Messaging platforms send you to hermes setup or ~/.hermes/.env instead of asking in chat. A plugin install prompts for any variables it declares and saves them to .env.
The documentation is direct about trust:
- By default, hub skills and plugin installs go through a security scan. A “dangerous” result blocks the install, even with
--force. - For plugins, the documentation says that “Cataloged ≠ audited”: a catalog listing “is not a code audit”. It recommends reviewing a plugin’s source before enabling it.
- The documentation says plugin capabilities are “a consent and audit layer, not isolation”. Third-party plugins run inside the Hermes process by default. The
plugins.isolationsetting moves them to a separate process, which is still not a sandbox.
Give a plugin credentials only after reading what it does with them.
On a hosted Hermes
Vavio runs your Hermes on a managed computer of its own, and the skills and credentials you add are stored on that computer. Vavio’s MCP server and CLI handle the computer, the model choice and gateway restarts. They don’t install or switch skills, tools or plugins today. Those choices stay with Hermes, and the distinctions in this article apply to your hosted Hermes just as they do elsewhere. A retest of the actual task is still the proof.
If you’re deciding where Hermes should run, compare running it at home or in the cloud and see the current hosting offer. Before updating to get a fix like the catalog limit, read how to update Hermes safely.
Sources
- Nous Research, skills, checked 11 November 2026
- Nous Research, tools and toolsets, checked 11 November 2026
- Nous Research, plugins, checked 11 November 2026
- Nous Research, MCP servers, checked 11 November 2026
- Nous Research, web dashboard, checked 11 November 2026
- Hermes v0.23.1 tool availability check, checked 11 November 2026
- Hermes v0.23.1 doctor tool report, checked 11 November 2026
- Hermes v0.23.1 plugin catalog size limit, checked 11 November 2026
- Hermes v0.23.1 release notes, checked 11 November 2026
- Vavio hosting and limits, checked 11 November 2026
Written by Vavio with AI assistance and checked against pinned Hermes v0.23.1 source, official documentation and release notes. No commands in this article were run for it.