The Best Hermes Agent Skills

We have not installed or run these ourselves, so treat this as a sourcing job, not a hands-on review: we read the actual SKILL.md files and repository metadata behind each pick rather than trusting another site's list. Full method is below the shortlist; skip straight there if you just want the recommendations.

The shortlist

Eight skills survived verification well enough to recommend by name. Where a skill is already bundled or in the official-optional set, there's nothing to compare it against for that job — it's the default-trusted option. Where we recommend an external repository, we say exactly how confident that recommendation is and why.

A note on that trust column: official here means it lives in the optional-skills/ folder of the main NousResearch/hermes-agent repo, which is a different claim from "written by Nous Research." Several of these (1password, duckduckgo-search, docker-management) are community-authored files that Nous Research folded into the official-trust tier — the SKILL.md frontmatter credits arceus77-7, gamedevCloudy, and sprmn24 respectively as authors. That's still meaningfully more vetted than a random GitHub repo — Nous Research chose to ship it as part of the project — but it's not the same as an in-house build. We're distinguishing the two explicitly rather than letting "official" imply more than it does.

Why each one, with the caveat that matters

Structured development discipline — test-driven-development, systematic-debugging, plan. These three bundled skills (plus the official-optional subagent-driven-development) are Hermes's own adaptations of obra/superpowers, a large, independently popular open-source agent-skills framework (MIT-licensed, actively pushed to as of this writing). The SKILL.md author fields say so directly: "Hermes Agent (adapted from obra/superpowers)". That lineage is a genuinely useful signal — you're getting a widely-used external methodology that Nous Research thought was good enough to adapt and ship by default, at zero install cost. Caveat: like any process/discipline skill, its value depends on whether you actually follow the RED-GREEN-REFACTOR and root-cause-first workflow it enforces; it can't make you use it.

subagent-driven-development — best for delegating implementation. Official-optional rather than bundled, so it needs an explicit install. It dispatches a fresh subagent per task with a two-stage (spec, then quality) review pass — useful once a plan from the plan skill is ready to execute. Same obra/superpowers lineage as above.

obsidian — best for vault-based note-taking. Bundled, and its SKILL.md credits "Teknium (teknium1), Hermes Agent" as author — a name closely associated with Nous Research's Hermes model work, for what that provenance is worth; we're reporting the credit as written, not independently confirming his role. It handles reading, searching, creating, and appending to vault notes directly on the filesystem. Caveat: it's filesystem-first — it expects a resolvable vault path, not a synced/cloud-only vault.

1password — best official secrets integration. Sets up the op CLI, signs in, and reads or injects secrets, gated behind a declared OP_SERVICE_ACCOUNT_TOKEN environment variable with a documented setup URL. This is the same skill the official docs themselves use as their canonical example of an official-tier install (official/security/1password), so it's about as well-attested as a recommendation on this page can get.

duckduckgo-search — best free fallback search. No API key required. Its frontmatter literally sets fallback_for_toolsets: [web], meaning it's designed to stay out of the way when a paid web-search toolset (Firecrawl) is configured, and step in automatically when it isn't — a concrete, verifiable instance of the conditional-activation mechanism described on the flagship page. Best pick if you don't want to configure a paid search provider at all.

docker-management — best for container workflows. Manages containers, images, volumes, networks, and Compose stacks with the standard Docker CLI — no extra dependencies beyond Docker itself, and it declares requires_toolsets: [terminal] so it won't surface in an environment without one.

composio-mcp — best broad SaaS/app integration. This is the one external, non-Hermes-specific pick on this list, so treat the confidence level differently from the rest. It's authored and maintained by ComposioHQ (Composio's own GitHub organization) in the composio-mcp-plugin repository, MIT-licensed, and its SKILL.md describes routing to "1000+ apps" through Composio's own MCP server rather than a per-service skill for each integration. Read that app count as Composio's own description of their product, not something we verified independently. Real caveats: the repository has very few stars (single digits) and hadn't been pushed to in several weeks as of this writing — low visibility for a first-party integration, so watch it for staleness before depending on it, and it's a generic MCP-plugin skill rather than something built for Hermes specifically (it works because Hermes implements the same agentskills.io format, not because Composio targeted Hermes).

manim-composer (from adithya-s-k/manim_skill) — best for technical animation. A dedicated, single-purpose repository (not a mega-registry) with genuine standalone traction — over a thousand GitHub stars, MIT-licensed. Same caveat as above: it's a generic skill package, not Hermes-specific, and it hadn't been pushed to in roughly seven months as of this writing, which is a real gap for anything depending on compatibility with a fast-moving Manim release. We're recommending it because it's the clearest standout we could independently verify for this specific, recurring need (3Blue1Brown-style math animation), not because it's actively maintained.

github-code-review + github-pr-workflow — best for GitHub PR workflow. Both bundled, both builtin trust, and designed to work together (each lists the other under related_skills, alongside a shared github-auth skill). Covers diff review with inline comments through gh or the REST API, and the branch → commit → PR → CI → merge lifecycle. If your work lives on GitHub, this pairing is already installed and ready.

What we deliberately left off

We looked hard at a general-purpose PowerPoint/.pptx skill and at several "awesome-hermes-skills"-style registries, because they show up repeatedly in searches. We didn't shortlist a specific .pptx skill: the candidates we found were scattered across dozens of unrelated multi-skill registry repos with no single standout maintainer or traction, and we're not going to name one as "best" just to fill out a category. If you need .pptx generation, search GitHub directly and vet what you find with the repository evaluation checklist — the demand for this capability is real, but the evidence doesn't support singling one repo out yet.

How we decided what belongs here

Five factors, applied roughly in this order of weight: provenance (bundled and official-optional skills get priority, since Nous Research has already chosen to ship them — external picks needed to clear a materially higher bar); documentation quality (does the SKILL.md actually explain what it does, needs, and how to invoke it — every skill above does); maintenance signal (commit/push recency and, where available, the skill's own version field — the only real observable signals; there's no download or usage telemetry for any of this); install friction (bundled and official-optional skills need zero or one command; the external picks need a full owner/repo/path install); and breadth vs. specificity (we tried to cover genuinely different jobs rather than eight overlapping options for the same task).

For the long tail beyond this list — narrow, single-integration community skills for a specific niche SaaS product or personal workflow — there are real, actively-committed repositories, but no basis for calling any particular one "best" over another with similar scope: star counts are low and close together, READMEs vary widely, and there's no independent usage signal. If you're in that position, evaluate the specific candidates yourself against the repository checklist rather than trust a ranked list — ours or anyone else's — that would be guessing at that scale.

Sources

• NousResearch/hermes-agent — optional-skills/ and skills/ folders — direct inspection of the SKILL.md files cited above (security/1password, research/duckduckgo-search, devops/docker-management, software-development/subagent-driven-development, note-taking/obsidian, software-development/test-driven-development, software-development/systematic-debugging, software-development/plan, github/github-code-review, github/github-pr-workflow)
• obra/superpowers — upstream framework credited in several bundled skills' author fields
• ComposioHQ/composio-mcp-plugin — skills/composio-mcp/SKILL.md
• adithya-s-k/manim_skill — skills/manim-composer/SKILL.md
• Hermes Agent — Skills System (official docs)
• Repository metadata (stars, license, last-push date) pulled directly via the GitHub API, August 2026