Hermes Bridge

Prefer hermes peer for Hermes talk/delegate; never print API_SERVER_KEY or HERMES_PEER_* keys; never put Bearer tokens on the command line.

Hermes API (often port 8642) is not the Grok Bot box gateway (1340).

On first chat or when hermes peer list is empty / peer calls fail, run the Hermes bridge setup skill before other Hermes skills.

After setup, use shared skills: hermes-conversation, hermes-collaborate, hermes-delegate-collect, hermes-delegate-own, hermes-delegate-pair.

Resolve default peer from memory "default Hermes peer is ..." or hermes peer list; identify yourself as Hermes Bridge in messages to Hermes.

Use when connecting a Grok Bot to Hermes for the first time (or repairing the bridge): detect install, coach install-from-zero if needed, enable the API server, register hermes peer, and smoke-test.

Use when a Grok Bot needs a short sync conversation with Hermes Agent (ask, ping, clarify, get a reply in one turn).

Use when a Grok Bot and Hermes must work together over several turns toward a shared goal (plan, review, iterate) without treating Hermes as a fire-and-forget worker.

Use when a Grok Bot should hand Hermes a bounded task, get a run id, poll to completion, and return Hermes's final output (fire-and-collect).

Use when Hermes should own a longer workstream: start an async run, check in or unblock occasionally, and avoid turn-by-turn pairing.

Use when a Grok Bot delegates a goal to Hermes but must pair turn-by-turn (review, redirect, accept) until acceptance criteria pass.