2026 Must-Have Hermes Agent Skills: The Most Complete List and Install Priority

2. What Hermes Agent Skills actually are

Skills are not a flat IDE plugin list. Each one is a workflow knowledge pack loaded on demand: a SKILL.md file describes when to trigger, what steps to follow, and which tools to use. The agent reads the full skill via skill_view only when the task matches—so you do not stuff every instruction into the system prompt.

• Install location: bundled skills copy to ~/.hermes/skills/ at install time; Hub skills use the same path (HERMES_HOME can override the root).
• Discovery: bundled Skills Catalog, Skills Hub (hermes skills browse), the agentskills.io ecosystem, and custom GitHub sources via hermes skills tap add.
• vs Tools: tools are capabilities (read files, run shell); skills are playbooks for recurring task types.

More installed skills does not mean a stronger agent—unused skills stay out of the token budget, but misinstalled high-permission skills widen the blast radius when triggered.

3. Commands you need before installing anything

These subcommands were checked against official docs on 2026-05-26. If anything changes, use the Skills System page and hermes skills --help. In chat, prefix with /skills for equivalent slash commands.

New installs take effect in new sessions; use /reset or --now on install to refresh the current session (higher token cost on the next turn).

4. Official bundled skills you should keep

Hermes copies the bundled library into ~/.hermes/skills/ at install; hermes update respects local deletes and user edits. The table below prioritizes engineering discipline—paths follow the official Bundled Catalog.

Office skills (google-workspace, notion) and research skills (arxiv) are enable when you have accounts; large creative packs can stay dormant until you need them.

5. External skills to prioritize on a fresh 2026 environment

Hub IDs, repos, and maintenance status change—this table gives decision data, not copy-paste install commands. Workflow: hermes skills search … → inspect → install.

6. Scene bundles: which group fits you

7. Skills you should not install without scrutiny

These belong in tier ④—not banned, but inspect, read source, and apply least privilege for authorized, compliant use only:

• Browser login state / Browser Use: may retain cookies; never run unauthorized bulk actions on banking, email, or social accounts.
• Cloud accounts & Composio: every connector expands leak surface—enable only what the task needs.
• X/Twitter (xurl), WhatsApp, full mailbox access: fine for low-frequency personal assist; not for spam or bypassing platform limits.
• Production repo write access: scope github-* workflows to branches and directories you trust.
• Anthropic-Cybersecurity-Skills, godmode, jailbreak packs: authorized test environments only—never abuse third-party services.

8. My 2026 Top 20 ranked list

Order balances beginner safety, dev velocity, content/research, automation, and long-term upkeep. “Bundled” needs no Hub install; “External” means search → inspect → install.

Reference numbers: the official bundled catalog lists 20+ categories and 100+ entries (verify on install day); Hub sources include official, skills-sh, well-known, and tap add custom repos. For a new machine, keep external installs ≤ 5, run stable for two weeks, then expand.

9. Why “install everything” fails in practice

1. Constraint: big lists feel like mandatory installs. Community READMEs rank by GitHub stars, not whether you use Obsidian or browser automation daily.
2. Hidden cost: high-permission skills expand audit surface. Every skill that can read mail, post socially, or drive a browser is a misfire risk—worse on a 24/7 gateway host.
3. Stability: install once, never maintain. Skipping check/update/audit leaves stale SKILL.md after Hermes upgrades.

10. Seven-step path you can run today

1. Validate Hermes itself: if not installed yet, follow the install & config guide; run hermes doctor with no fatal errors.
2. List bundled skills: hermes skills list vs section 4; restore gaps with hermes skills reset --restore if needed.
3. Pick one scene bundle: choose one row from section 6 and name only 2–3 external skills to add.
4. Inspect each candidate: hermes skills search … then hermes skills inspect <id>; pass the section 7 checklist.
5. Install and sandbox: hermes skills install <id>; test in ~/hermes-lab, not a production repo.
6. Verify in a fresh session: /reset or a new hermes chat; confirm skills trigger as expected.
7. Calendar maintenance: weekly skills check, monthly skills audit; align with the long-term maintenance guide backup policy.

11. Post-install maintenance

• Update on a schedule: hermes skills check → hermes skills update (run hermes backup before major Hermes upgrades).
• Reset when bundled skills break: hermes skills reset NAME --restore.
• Remove unused high-permission skills: hermes skills uninstall plus skills config to disable on gateways.
• Capture real workflows: use hermes-agent-skill-authoring or Skill Factory to author your own skills instead of hoarding Hub trends.