How does Hermes work with skills?
Hermes Agent follows the same open standard. According to the skills documentation, all skills live in one folder per profile. Every skill is also a command. Type a slash and the name of the skill, in the terminal or in a chat channel, and the agent opens that workflow right away.
Hermes also writes skills on its own. When the agent has worked out a multi-step task, fixed an error, or you correct its approach, it saves that as a skill. Next time, the agent does not start over. With the /learn command, you can turn a manual, a web page, or a workflow you just showed the agent into a skill. Hermes keeps small facts that always apply in its memory. Longer workflows go into a skill.
By default, Hermes writes those skills without asking. If you want to see every change first, turn on approval for skills. A new or changed skill then waits until you approve it. For a business, that is often the better choice. You can read more about what Hermes does in Hermes Agent explained. How Voltti sets up the agent for businesses is on the page about the Hermes AI agent.
How do you manage skills across a team?
Our advice for teams: put your team’s agent skills, plug-ins, and MCP servers in a GitHub repo owned by your company. Install them on every Hermes setup from there. A skill that lives only on one colleague’s laptop does not help the rest of the team. And if everyone keeps their own version, the agent does the same job three different ways. With one shared repo, the team works on one workflow, and you can see who changed what.
Hermes supports this in a few ways. You can add a GitHub repo with skills as a source and install skills from it. You can also have Hermes read an extra folder, such as a copy of that repo on the computer where the agent runs. And you can have the skills the agent writes itself land in a folder under version control. Here is how to go about it:
Start small, with one skill for a task that comes back every week, such as a report or a quote.
Write a description that says when the skill fits, and keep the workflow short and concrete.
Have a colleague review every change to a skill, just as you would with code.
Turn on approval for skills so the agent can’t change the team’s workflow on its own.
Be careful with a shared folder. According to the documentation, Hermes can edit skills in a shared folder if it has write access there. If you don’t want that, make the folder read-only.
If your business has several departments, each department can get its own profile with its own skills. You can read how that works in Hermes for teams.
Can you use skills made by others?
Yes, and that can be useful: there are public collections with thousands of agent skills. But a skill is more than text. It can contain scripts that the agent runs. It can also contain instructions that make the agent do things you don’t want. A January 2026 study (a preprint) analyzed 31,132 skills from two large public marketplaces and found at least one vulnerability in 26.1% of them.
Hermes runs a skill from an outside source through a security scan first. The scan looks for data leaks, hidden instructions, and commands that cause damage, among other things. If the scan marks a skill as dangerous, Hermes won’t install it, even if you try to force it. Still, a scan does not replace your own review. Read a skill before you install it, and pay special attention to the scripts. Anthropic gives the same advice: "We recommend installing skills only from trusted sources."
You’ll find more measures in our checklist for AI and business data. For how Hermes compares to another open-source agent with its own skills, read Hermes vs OpenClaw.
How does Voltti use skills itself?
Our own Hermes setup at Voltti uses skills for work that comes back. A skill for content planning, for example, sets which Search Console data the agent pulls and how it turns that data into a content calendar. Each environment has its own settings and its own skills. That way, the agent does not use the workflow of one job for another. The agent keeps our knowledge base with the official llm-wiki skill, which you install separately in Hermes. That knowledge base has one note per topic with its sources, plus an index and a log. During a security audit, the agent follows Voltti’s own skills, with fixed work instructions for each type of check. You can read how that works in how Voltti runs a security audit.
A skill does not make an agent smarter than the language model behind it. What a skill does is make the agent handle the same task the same way every time, with the lessons from last time included. To see how an agent also runs this kind of work on a schedule and with helper agents, read agentic workflow.
Where do you start with agent skills?
Pick one task your colleagues do the same way every week, and write down how it goes. That is your first skill. Let the agent run the task a few times, compare the result with your team’s work, and improve the skill. In a pilot, you test this with the access the task needs, and no more. A pilot usually takes 2 to 4 weeks, from the first conversation to the evaluation. You can read how that works in our approach.