Hermes-WorkBuddy Communication Bridge for Openclaw

A robust communication bridge that enables bi-directional, asynchronous messaging between WorkBuddy and Hermes via a shared JSON file queue.

liuboacean
v1.2.0
Apr 20, 2026
0
197
1

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install hermes-communication-bridge

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install hermes-communication-bridge using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Hermes-WorkBuddy Communication Bridge?

The Hermes-WorkBuddy Communication Bridge is a specialized tool within the Openclaw Skills ecosystem designed to facilitate direct interaction between independent AI agents. By utilizing a shared file system approach at ~/.hermes/shared/communication/queue.json, it allows agents to exchange tasks, queries, and status updates without requiring complex API integrations or constant network connectivity.

This skill serves as a reliable middleware, ensuring that messages are not lost during transit through the use of a persistent history log and a nanosecond-precision unique ID system. It is ideal for developers who need to orchestrate multi-agent workflows where WorkBuddy acts as the primary interface and Hermes handles background autonomous operations.

Hermes-WorkBuddy Communication Bridge Use Cases

  • Coordinating complex tasks between WorkBuddy and Hermes agents using Openclaw Skills.
  • Triggering background system commands or file transfers from a chat-based interface.
  • Monitoring agent status and health through asynchronous query-response cycles.
  • Implementing alert systems where Hermes can push notifications to the WorkBuddy queue.

How Hermes-WorkBuddy Communication Bridge Works

  1. WorkBuddy initiates communication by appending a JSON-formatted message to the shared queue file using the send command.
  2. The Hermes agent, via a cron job or an automated poller, monitors the queue for any messages marked with a pending status.
  3. Hermes processes the request and writes a response back to the queue, addressing it to workbuddy.
  4. WorkBuddy retrieves the reply using the receive command, allowing the user to view the agent's output.
  5. The communication cycle concludes when the message is marked as completed, moving the record from the active queue to history.

Hermes-WorkBuddy Communication Bridge Setup

To install and configure this bridge within your Openclaw Skills environment, ensure the Python scripts are placed in the correct directory and the shared folder exists.

# Create the shared communication directory
mkdir -p ~/.hermes/shared/communication/

# Ensure scripts are executable
chmod +x ~/.workbuddy/skills/hermes-communication-bridge/scripts/communication_queue.py

# Test the connection by sending a ping
python3 ~/.workbuddy/skills/hermes-communication-bridge/scripts/communication_queue.py send workbuddy hermes "System Check"

Hermes-WorkBuddy Communication Bridge Data Schema & Taxonomy

The skill manages data using a structured JSON schema to maintain consistency across different Openclaw Skills implementations.

Field Type Description
id String Unique nanosecond timestamp (e.g., msg_1713254400000000_workbuddy)
sender Enum The origin agent: workbuddy or hermes
type Enum message, task, query, response, status, file, command, or alert
priority Enum low, normal, high, or urgent
status Enum pending, processing, completed, or failed

Hermes-WorkBuddy Communication Bridge Advanced Features

  • Nanosecond ID Generation: Version 1.1.0 introduced time.time_ns() to prevent ID collisions during high-frequency messaging.
  • Multi-Type Support: Handles diverse data payloads including system commands and file transfer metadata.
  • Idempotent Processing: Built-in status tracking ensures that messages are only processed once by the receiving agent.
  • Coexistence Support: Fully compatible with the hermes-memory-bridge for users requiring both queue-based and event-driven architectures.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*