Hermes Skill Bundles Make Agent Workflows Feel Native
Hermes just introduced skill bundles. They turn repeatable agent workflows into one slash command, so users can name a job once and let Hermes load the right skills and instructions every time.
Hermes just shipped skill bundles.
Nous Research announced it here on X: Introducing skill bundles. The docs explain them under Skill Bundles.
A bundle gives a recurring job one slash command.
For example, a release-prep bundle can load the skills and instructions for changelog, docs, QA, and rollout notes.
The user does not need to remember the skill stack. The command names the work.
Use bundles for recurring jobs
Good bundle names are job names:
| Bundle | Job |
|---|---|
/release-prep | Changelog, docs, QA checklist, rollout notes. |
/incident-response | Logs, debugging, status updates, postmortem. |
/research-brief | Sources, synthesis, final brief. |
Bad bundle names are toolbox names.
A bundle should answer one question:
What job am I starting?Not:
What pile of skills might be useful someday?Bundle the workflow, not the kitchen sink
Research → ideate → write → critique is a workflow.
Code review → tests → PR is a workflow.
Logs → diagnosis → fix → postmortem is a workflow.
Five unrelated skills under one command is not a workflow. It gives Hermes more instructions and less direction.
That is the whole rule: bundle the job you actually repeat.
Agent Analytics as one example
Product analytics work has the same shape.
When Hermes reviews product behavior, it needs context:
- what the product does
- what user progress means
- which event counts as activation
- which funnel matters
- what kind of recommendation is useful
A product bundle might be:
/product-growth-loopIt can load Agent Analytics plus the product rules Hermes should apply when reading the data.
That is the same pattern as /release-prep: the slash command names the job, and Hermes loads the right context behind it.
Ask Hermes to create the bundle
Do not start by copying terminal commands.
Ask Hermes:
Create a Hermes skill bundle called /product-growth-loop.
Use the current product context and Agent Analytics.
When I run it, inspect product behavior, find the biggest bottleneck, and recommend the next measured improvement.
Show me the bundle and one example prompt.The user names the job. Hermes should already have the product context and Agent Analytics available.
If someone wants the file format, the Hermes docs have the YAML schema. The product workflow should not begin there.
Name it after the work
Use plain names:
/release-prep
/incident-response
/research-brief
/product-growth-loopFor a product bundle, the instruction can stay short:
This product helps teams understand what users do after signup.
Use Agent Analytics to review the funnel from visit to meaningful activation.
Treat activation as the first completed project, not account creation.
Recommend one product change and one event or funnel that proves whether it worked.
Do not optimize for raw traffic if activation gets worse.This beats:
Use analytics.Now Hermes has the product rule, not just the tool name.
What changes in daily use
Without a bundle:
Use the analytics skill. Remember activation means project_created. Ignore raw traffic unless it leads to setup. Compare the docs flow to signup and activation. Recommend one measured product change.With a bundle:
/product-growth-loop inspect the docs-to-activation path for the last 14 daysThe repeated context moves into the bundle. The prompt stays about today’s task.
Keep bundles narrow
Do not make an everything bundle.
Start with one recurring job. If another workflow repeats, create another bundle.
Small named workflows beat one giant context dump.
Example prompt
/product-growth-loop
Inspect my docs-to-activation path for the last 14 days.
Apply the product rules from this bundle.
Find the biggest leak between docs visit, signup, and activation.
Recommend one change Hermes should make next.
Tell me which event or funnel should prove whether it worked.Skill bundles remove repeated setup from work you already do.
Related: Hermes installation guide · You Can Now Scale Depth as Well as Width With Hermes Subagents. Agent Analytics Got 140% More Growth Bets · Project Context, Portfolio Context, and Self-Improvement for AI Agents · If You Use Hermes to Handle Your Projects, You Need Agent-Readable Web Analytics
