Awesome Lists & Community Resources

21.2. Awesome Lists & Community Resources — The Community Use-Case Collection

The standout list: awesome-hermes-usecases

github.com/aliaihub/awesome-hermes-usecases

The most notable feature of this repository is its “evidence rule” — every use case listed must link back to a verifiable origin: the official Hermes documentation, a Nous Research companion repository, a GitHub issue with real implementation details, or a first-person blog post. This is why this repository is more trustworthy than the usual “10 ways to use X” blog posts — every claim is traceable, in the exact spirit of the Sourced Reports described in chapter 14.5.

A few notable real-world examples from this repository

• Combining Matt Pocock’s open-source planning skills (/grill-me, /to-prd, /to-issues) for up-front scoping, then handing off to Hermes subagents that implement the subdivided issues in parallel as vertical slices — with a human-in-the-loop (HITL) gate to block low-quality AI code before merge. This is a direct illustration of how to combine chapter 13.2 (Parallel Work) with chapter 15.5 (Pull Requests).
• A self-monitoring improvement loop that reads session history, ranks the weakest skills, proposes patches or new skills, and reports on learning progress — a direct extension of the mechanism described in chapter 20.
• The /kanban command (since v0.15) turns a single Slack message into a persistent multi-agent “swarm” with named workers, a verifier, and a synthesizer — persistently stored via ~/.hermes/kanban.db, exactly the mechanism described in detail in chapter 13.3.
• One always-on shared bot for a small team (coding, research, ops) with per-user sessions, Docker-isolated terminals, and an allowlist — the gateway also supports Discord, Slack, WhatsApp, Signal, Matrix, Email, SMS, and more; the Telegram flow is usually the cleanest starting point for any of those platforms.
• Production-style deployments on Chinese enterprise chat platforms — Feishu managed via launchd, WeCom with native media analysis and vision.

Notes

• Before designing a complex workflow from scratch, check this repository to see if someone has already done something similar — many patterns (HITL gates, swarms via Kanban) have been proven in practice.
• For use cases involving security or production, always follow the link to the verifiable origin rather than trusting the summary description alone — this repository’s evidence rule exists precisely for that purpose.
• “Awesome list” community repositories usually update faster than the official documentation for just-launched features — useful for keeping up with the latest use cases, but always cross-check against 21.1 when you need exact technical details.