Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Skill & Plugin Catalogs

21.3. Skill & Plugin Catalogs — Finding Extensions by Function

Skills Hub — covered in detail in chapter 10.2

The central lookup point when you need a specific skill you do not have yet, organized by source: official (in the main repository), skills-sh (the Vercel hub), well-known (sites self-publishing via /.well-known/skills/index.json), github (direct taps such as openai/skills, anthropics/skills, NVIDIA/skills), clawhub, lobehub, browse-sh (200+ browser-control skills for specific sites).

hermes skills search <keyword>
hermes skills inspect <source>/<skill name>

Always inspect before installing — the security principle from chapter 10.2, especially for community-sourced skills that have not been carefully vetted.

The open agentskills.io standard

Mentioned in chapter 20.4: Hermes skills are compatible with this standard, meaning a skill written for Hermes can be ported to other agents supporting the same standard, and vice versa — a skill written to the agentskills.io standard elsewhere usually plugs into Hermes with little modification. Worth a look if you plan to write skills for broad sharing outside the Hermes ecosystem.

The complete list of bundled skills

In the skills/ directory of the main repository (21.1) — organized by category (research, github, google-workspace…), each skill has a SKILL.md you can read directly on GitHub before deciding whether you need to install it.

Notes

  • Before writing a skill from scratch (chapter 10.4, /learn), always run hermes skills search first — chances are someone has already written it, especially for common tasks (GitHub, Google Workspace, monitoring).
  • For sharing skills internally within a team, consider publishing to the agentskills.io standard from the start instead of writing in a structure that only works inside Hermes — this preserves reusability later if the team moves to another tool.
  • Read the SKILL.md directly on GitHub (not just the short description) before installing any skill that affects important systems — the short description is not enough to fully assess the skill’s pitfalls and its real scope of action.