Hermes Agent Skills on GitHub

Start with the official repository

The canonical source is github.com/NousResearch/hermes-agent itself — MIT licensed. Bundled skills and the optional-but-official skill set both live inside this repo, under optional-skills/ and skills/. These carry builtin or official trust automatically; nothing else on GitHub does.

What we found searching GitHub directly

Rather than link to whatever ranks well on search engines, we ran GitHub's own repository search for Hermes-skill-related projects. Here's what's actually out there, described accurately rather than promotionally:

Repository	What it actually is
`ChuckSRQ/awesome-hermes-skills`	A curated collection spanning brainstorming, PRD workflows, debugging, Apple integrations, MLOps, and document processing. Positioned as curated rather than exhaustive.
`codesstar/hermes-skill-atlas`	Describes itself as an "interactive map" claiming 70+ curated, verified skills. The "verified" claim is the repo's own, not an independent audit.
`itgoyo/hermes-skills`	Claims 310+ skills across many domains. At that scale, breadth is very likely coming at the cost of per-skill curation — treat this as a wide net to search, not a pre-vetted shortlist.
`aibuild-lab/skills-guard`	Not a skill catalog — an MIT-licensed port of Hermes's own `skills_guard.py` scanner, useful as a standalone security/trust-matrix tool if you want to scan a skill outside of `hermes skills install`.
`cosmicstack-labs/mercury-agent-skills`	A registry positioned as cross-compatible across Mercury Agent, OpenClaw, and Hermes — useful if you want a skill that works outside Hermes too, but cross-compatibility claims are worth checking against the actual `SKILL.md` files, not just the registry's README.

Beyond these, there's a long tail of narrow, single-purpose repositories — integrations for specific note-taking apps, self-hosted services, social platforms, and niche personal workflows. They're real and often well-built, but there are too many, too undifferentiated, and too fast-changing for any static list (including this one) to stay accurate. Search GitHub directly for hermes agent skill <what you need> and evaluate what comes back using the checklist below.

How to evaluate a skill before installing it

None of this replaces Hermes's own security scan on hub installs — it's what to check in addition, especially for anything at community trust tier (see trust tiers).

1. Does SKILL.md match the actual spec? It needs name and description at minimum. If the repo is missing a SKILL.md entirely, or has one that doesn't follow the format Hermes expects, it's not going to progressive-disclose correctly — at best it won't load, at worst it'll load as an oversized blob every time.

2. Is the description honest and specific? An overly broad description is a real functional problem, not just bad style — it means the skill will get matched to tasks it shouldn't, competing with more relevant skills. Vague, marketing-style descriptions ("does everything you need!") are a signal of a low-quality skill even before you read the instructions.

3. What does it declare it needs? Check required_environment_variables in the frontmatter and any setup instructions in the README. A skill that silently expects an API key without declaring it, or that expects tools/toolsets it doesn't list under requires_tools, will fail unpredictably instead of failing clearly.

4. What do the bundled scripts actually do? If the skill ships a scripts/ folder, read it — especially anything that shells out, writes files outside the skill directory, or reaches the network. This is exactly what Hermes's own scanner checks for (data exfiltration, prompt injection, destructive commands), but a scanner is a floor, not a substitute for reading code you're about to let an agent execute with your credentials.

5. How recently was it actually touched? Last commit date and commit frequency are the only real proxies available for "is this maintained." Star count tells you about visibility, not upkeep — a skill with many stars and no commits in months is a different risk profile from one with fewer stars and active maintenance.

6. Does it match its own claims? If a repo claims a specific skill count ("70+", "310+"), spot-check a handful rather than trusting the number — repo-level claims about a skill collection are the repo's own marketing, not a verified fact, and we're treating them the same way in this guide: attributed, not restated as fact.

7. License. Check it has one, and that it's compatible with how you intend to use the skill (personal use vs. redistributing inside a team fork, for instance).

Installing what you find

Once you've picked a repo, install directly by path:

hermes skills install <owner>/<repo>/<skill-path>

or subscribe to it as an ongoing source:

hermes skills tap add <owner>/<repo>

Full command reference: how to install Hermes Agent skills.

Sources

NousResearch/hermes-agent (GitHub)
Hermes Agent — Skills System (official docs)
Live GitHub repository search conducted August 2026 for Hermes-skill-related repositories