grok-bot:R8ZaqL5ZH9x4PjtsGsar5
Ultimate Hermes Grok Bridge
Runs a Hermes agent alongside Grok bots with either side able to take the lead over HTTP or SSH
Overview
This puts a hermes agent bot inside your grokbot app, and let's you use either Hermes as Chief of Staff over Grokbot, or the other way around! Now your whole fleet is in your pocket with a beautiful voice!
Contents
- skill Ultimate Hermes↔Grokbot bidirectional Use when wiring or operating any talk path between Grok Bot and Hermes in either direction (HTTP :8642, SSH relay, Hermes CLI, Tailscale webhook), or when choosing which path to use.
- skill Getting started — Hermes↔Grokbot bridge Use on the first conversation after importing the Ultimate Hermes↔Grokbot Bridge template — ask setup questions one at a time, then smoke both directions.
- skill Hermes HTTP-only talk path Use when talking to fleet Hermes, wiring hermes-* connectors, or anytime SSH relay tempts as a fallback — SOLE PATH is HTTP :8642.
- skill hermes-bridge-method-chooser Use when deciding between Hermes SSH Relay and Hermes API Fleet (:8642) for putting Hermes inside Grok Bot — fleet default is HTTP-only.
- skill Wire Hermes native API Use when an installer needs to enable Hermes :8642, verify health, or add a Tailscale-reachable hermes-<hostname> connector in Grok Bot.
- skill hermes-ssh-relay-setup Use when installing or wiring the Hermes SSH ask-relay MCP so a Grok Bot can talk to a Desktop-primary Hermes host over Tailscale.
- skill Grok Bot computer update survival (Tailscale) Use this when setting up Tailscale (or any installed tool, daemon, or key) on the Grok Bot computer, when the computer may have been updated or reset, or when the bot can't reach tailnet hosts. It makes the setup survive a Computer Update and restore itself with no human step.
- skill Tailscale fleet macOS PUBLIC SANITIZED. Use for Public templates and Tailscale recovery with placeholders only — no live IPs, MagicDNS tails, machine names, secrets, or keys.
- skill hermes-fleet-messaging-token-isolation use this when documenting Hermes fleet Bitwarden secrets for messaging bots or any per-host credential — never share one TELEGRAM_BOT_TOKEN (or other per-host key) across hosts; store only FOO_<PROFILE> so Hermes auto-aliases per active profile
- memory Memory entries · 11 items
Dependencies
No plugin dependencies are declared.
Attachments
No separate attachments are published for this record.