Hermes Agent Official Bundled
vs Community Skills: Your 2026 Must-Install List

A steadier approach is layered: official bundled skills are the base (planning, debugging, TDD, review, GitHub, MCP, productivity, research), and community / Hub skills are enhancements (cloud browsers, SaaS bridges, page cleaning, deeper testing, long-running workflows). Chasing only Hub trends invites overlap, bloat, and high-privilege risk; staying bundled-only may leave a real gap in your task chain.

1Official bundled = base; community = enhancement

After install, bundled skills copy into ~/.hermes/skills/, sync on hermes update, and respect local edits. Skills under optional-skills/ need hermes skills install official/<category>/<skill>. Community skills install via the Skills Hub (skills-sh, well-known, direct URLs, etc.); third-party sources get security scans—still run hermes skills inspect before you trust one.

2Bundled skills to keep by default

Most users should know and keep these bundled capabilities (paths under ~/.hermes/skills/):

Accidentally removed a skill? Use hermes skills reset <name> --restore to pull it back from bundled. On Mac, optional apple/macos-computer-use and imessage are useful—tighten approvals and directory boundaries in production.

3Community skills to install first

Add Hub skills when bundled coverage exists but is shallow, or when an integration is missing. Install IDs change—trust hermes skills inspect at install time:

4Where capabilities overlap

• →Human-like writing: bundled humanizer vs Hub SEO packs—add SEO when you need keyword/structure templates, not for every draft.
• →Planning: plan / writing-plans cover daily work; add kanban-orchestrator only for Kanban-style orchestration.
• →Browser: built-in Chromium tools + Browser Use = cloud sessions and anti-detection; skip if you do not need cross-border logins.
• →Knowledge base: llm-wiki for self-hosted wikis; deepen either bundled Obsidian or Hub extensions—not both by default.
• →MCP: native-mcp wires servers; Composio MCP wires SaaS—do not register the same tool twice.

5Scene-based stacks (bundled base + Hub boost)

• →Development: plan + TDD + github-pr-workflow + requesting-code-review; optional Browser Use for docs behind login walls.
• →SEO content sites: writing-plans + humanizer + Defuddle for competitor pages; Hub SEO skills as add-ons.
• →Research: arxiv + blogwatcher + Defuddle; llm-wiki or Obsidian extensions for storage.
• →Office automation: google-workspace + Composio; webhook-subscriptions for cron-style triggers.
• →Web testing: TDD + Playwright skill + dogfood for exploratory QA.

6Pre-install checklist for community skills

• 1Source: prefer official/ and skills-sh/; unknown URLs require inspect
• 2Scripts: read shell/Python referenced in SKILL.md—no obfuscation
• 3Network: note unknown domains; restrict egress on production hosts
• 4Secrets: minimal OAuth/API scope; never commit keys to project Git
• 5Filesystem: default working dir, full-disk or Keychain access requests
• 6Maintenance: recent commits, responsive issues
• 7After install: hermes skills list; load in session via /reset or --now

72026 Top 20 recommendations

For install and Gateway basics, see our Hermes install & setup guide and Mac setup checklist.

8Layered skill management is easier on Mac mini

Skills call terminals, browsers, and local files. macOS gives you native Unix, launchd for a persistent Gateway, and a Docker terminal backend—without WSL friction on Windows. Mac mini M4 draws about 4W at idle; unified memory suits always-on Hermes plus browser automation. Gatekeeper, FileVault, and manual approval modes reduce exposure from high-privilege community skills.

If you are building a production agent with “bundled base + a few Hub extensions” from this list, Mac mini M4 is a strong value host. Get one now and run Skills on hardware built for long uptimes.