Tool
Hermes Skill Library: Browse, Inspect, and Audit Skills
Use the Hermes skill library safely: browse sources, inspect procedures before installing, test outcomes, audit updates, and remove stale skills.
Quick answer
Use `hermes skills browse` and `search` to discover skills, `hermes skills inspect` to review a candidate, and `hermes skills install` only after checking commands, scripts, permissions, and overlap. Audit and remove skills that do not pass a real task.
The Hermes skill library is a discovery catalog, not a recommendation to install everything. Search broadly, inspect carefully, and keep a small trusted set that improves repeat work.
Features
- ✓Skill browsing across supported sources
- ✓Pre-install inspection
- ✓Security scanning for external installs
- ✓Update and audit lifecycle
- ✓Community publishing
Why this tool matters
Hermes supports browsing and searching across configured skill sources. Use the installed CLI for current identifiers rather than relying on an old directory URL.
Preview candidates with `hermes skills inspect <id>`. Review trigger scope, shell commands, helper scripts, URLs, environment variables, tools, and verification steps before installation.
External installs run a security scan, but source review and a restricted test remain necessary. A scanner cannot prove that a procedure is correct or appropriate for your environment.
Maintain the set with `hermes skills audit`, `check`, `update`, and `uninstall`. Re-run a fixed acceptance test after changes and remove overlap or context bloat.
Best use cases
FAQ
Run `hermes skills inspect <skill-id>` and review the trigger, procedure, commands, scripts, URLs, environment variables, tools, and acceptance checks.
Installation scans external skills, but you should still review source and test with restricted permissions. Treat helper scripts and operational commands as third-party code.
Use `hermes skills list`, `audit`, `check`, `update`, and `uninstall`. Keep only skills that match repeated work and still pass a bounded test.