← Back to Skills Marketplace

Hermes Communication Bridge

Name: Hermes Communication Bridge
Author: liuboacean

by liuboacean · GitHub ↗ · v1.2.0 · MIT-0

cross-platform ✓ Security Clean

123

Downloads

Stars

Active Installs

Versions

Install in OpenClaw

/install hermes-communication-bridge

Description

WorkBuddy 与 Hermes 之间通过共享文件队列直接通信。触发词：发消息给hermes、收hermes消息、查看通信队列、双向通信、队列消息、异步通信

README (SKILL.md)

Hermes-WorkBuddy 通信桥

v1.x 注意：此为队列式通信桥（queue.json）。如需更强大的事件驱动闭环命令系统，请改用 hermes-memory-bridge v2.0（~/.workbuddy/skills/hermes-memory-bridge/）。两者可并存，各司其职。

通过 ~/.hermes/shared/communication/queue.json 共享文件队列，WorkBuddy 与 Hermes 直接双向通信。

核心文件

队列：~/.hermes/shared/communication/queue.json
历史：~/.hermes/shared/communication/history.json
技能：~/.workbuddy/skills/hermes-communication-bridge/scripts/communication_queue.py

CLI 命令

# WorkBuddy → Hermes 发消息
python3 ~/.workbuddy/skills/hermes-communication-bridge/scripts/communication_queue.py send workbuddy hermes "内容"

# 收 Hermes → WorkBuddy 的消息
python3 ~/.workbuddy/skills/hermes-communication-bridge/scripts/communication_queue.py receive workbuddy

# 查看队列统计
python3 ~/.workbuddy/skills/hermes-communication-bridge/scripts/communication_queue.py stats

# 标记消息已处理
python3 ~/.workbuddy/skills/hermes-communication-bridge/scripts/communication_queue.py mark \x3Cmsg_id> completed

消息格式

{
  "id": "msg_\x3Ctimestamp>_\x3Csender>",
  "sender": "workbuddy|hermes",
  "receiver": "hermes|workbuddy",
  "type": "message|task|query|response|status|file|command|alert",
  "content": "消息内容",
  "priority": "low|normal|high|urgent",
  "status": "pending|processing|completed|failed"
}

类型说明

message：普通文本消息
task：任务请求（带元数据）
query：查询请求
response：响应
status：状态更新
file：文件传输
command：系统命令
alert：警报通知

工作流

WorkBuddy 发消息：send workbuddy hermes "内容"
Hermes 读取：通过 cron 或 auto_poller 轮询队列，发现 pending 消息
Hermes 回复：写 hermes → workbuddy 的 pending 消息
WorkBuddy 读取：receive workbuddy，处理消息
标记完成：mark \x3Cmsg_id> completed

版本历史

v1.1.0（2026-04-16）

Bug Fix：修复消息 ID 秒级时间戳碰撞问题，改用 time.time_ns() 生成纳秒级唯一 ID，避免同一秒内多条消息 ID 重复
Hermes 侧安装说明：process_queue.py 和 communication_queue.py 需同时安装到 Hermes skill 目录（~/.hermes/skills/autonomous-ai-agents/hermes-communication-bridge/），Bridge cron 才能正常工作
验证通过：双向通信延迟约 1 分钟，队列幂等处理正常

v1.0.0（2026-04-16）

初始版本发布

Usage Guidance

This skill is coherent and implements a local file queue; the main things to check before installing: (1) Confirm the Hermes-side consumer (process_queue or other Hermes skills) does NOT execute arbitrary 'command' messages or automatically write/execute files — if it does, that creates execution risk. (2) Ensure the queue directory (~/.hermes/shared/communication or your custom HERMES_COMM_QUEUE_DIR) has appropriate file permissions and is not shared with untrusted users/processes. (3) Be aware queue file writes are simple JSON file writes without locking — concurrent writers/readers could cause corruption; use only in single-user environments or add locking. (4) The repo contains duplicate temp-repo2 files (likely packaging leftovers); they are redundant but harmless. If you will send sensitive data, avoid this channel unless you add encryption or a safer transport and verify the consumer's behavior.

Capability Analysis

Type: OpenClaw Skill Name: hermes-communication-bridge Version: 1.2.0 The skill implements a local Inter-Process Communication (IPC) bridge between two agents (WorkBuddy and Hermes) using a shared JSON file queue located in the user's home directory. The code in 'communication_queue.py' and 'hermes_comm.py' is standard Python logic for managing file-based message persistence and lacks any indicators of data exfiltration, obfuscation, or unauthorized command execution. While the configuration defines a 'command' message type, the provided scripts only facilitate message transport and do not contain logic to execute shell commands or system calls.

Capability Tags

crypto

Capability Assessment

✓ Purpose & Capability

Name/description claim a local file-queue bridge and the package contains Python scripts that create/read/write ~/.hermes/shared/communication/queue.json and provide CLI helpers — these requirements align with the stated purpose. The duplicated temp-repo2 files appear to be packaging duplicates, not extra capabilities.

ℹ Instruction Scope

SKILL.md instructs only to read/write the shared queue files and run included scripts — scope matches the bridge purpose. Note: the message schema includes types 'command' and 'file'; this skill itself only stores messages and does not execute commands or transfer files, but those message types could enable dangerous behavior if the Hermes side (or any consumer) executes message contents. Review the Hermes-side consumer before trusting messages that carry commands or file payloads.

✓ Install Mechanism

No install spec (instruction-only) and code files bundled with the skill. Nothing is downloaded from external URLs or written to nonstandard system locations beyond user home directory; no packaging/install scripts are included.

✓ Credentials

The code optionally respects a single env var (HERMES_COMM_QUEUE_DIR) to override queue location; SKILL.md and files request no credentials or unrelated environment variables. Config files contain a hard-coded example path (/Users/liubo) which is benign but user-specific.

✓ Persistence & Privilege

Skill is not always-enabled and uses normal autonomous invocation defaults. It stores queue files under the user's home directory (creates ~/.hermes/shared/communication) which is appropriate for its function and does not modify other skills or system-wide settings.

How to Use

Make sure OpenClaw is installed (local or Docker)
Run the install command in chat: /install hermes-communication-bridge
After installation, invoke the skill by name or use /hermes-communication-bridge
Provide required inputs per the skill's parameter spec and get structured output

Version History

v1.2.0

- Enhanced documentation with notes distinguishing the queue bridge from the event-driven `hermes-memory-bridge` system, including migration advice. - Updated description to include more usage triggers such as queue messages and async communication. - No code or workflow changes; this update is focused on clarifying usage scenarios and recommended upgrade paths in SKILL.md.

v1.1.0

Bug Fix: 修复消息 ID 秒级时间戳碰撞，改用纳秒级 time_ns()。新增 Hermes 侧安装说明文档。

v1.0.0

Initial release — enables direct file-based message exchange between WorkBuddy and Hermes. - Adds a shared queue (`queue.json`) for bidirectional communication. - Supports multiple message types (text, task, query, etc.) and priorities. - Provides CLI for sending, receiving, and managing messages. - Tracks message history and processing status. - Includes sample workflows and detailed message format specification.

Metadata

Slug hermes-communication-bridge

Version 1.2.0

License MIT-0

All-time Installs 0

Active Installs 0

Total Versions 3

Frequently Asked Questions

What is Hermes Communication Bridge?

WorkBuddy 与 Hermes 之间通过共享文件队列直接通信。触发词：发消息给hermes、收hermes消息、查看通信队列、双向通信、队列消息、异步通信. It is an AI Agent Skill for Claude Code / OpenClaw, with 123 downloads so far.

How do I install Hermes Communication Bridge?

Run "/install hermes-communication-bridge" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Hermes Communication Bridge free?

Yes, Hermes Communication Bridge is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Hermes Communication Bridge support?

Hermes Communication Bridge is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Hermes Communication Bridge?

It is built and maintained by liuboacean (@liuboacean); the current version is v1.2.0.

More Skills