Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Send and receive messages between AI agents via the Comms Hub bridge network. Use when communicating with other agents (Aristotle, Daedalus, Thales, Steel Ma...
Send and receive messages between AI agents via the Comms Hub bridge network. Use when communicating with other agents (Aristotle, Daedalus, Thales, Steel Ma...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Agent-to-agent messaging via a shared Comms Hub server. Supports send, receive, acknowledge, file sharing, and presence.
Copy config.json.example to config.json in this skill folder Edit config.json with your hub connection details and agent name All commands use node scripts/bridge-client.js <command>
FieldRequiredDescriptionhubIpYes*Hub server IP (use when SNI/Host header needed)hubHostYes*Hub hostname (used as Host header if hubIp set, or as hostname if hubIp empty)hubPortNoPort (default: 443)hubProtoNohttps or http (default: https)agentNameYesYour agent's name on the bridge (lowercase) *At least one of hubIp or hubHost is required. Environment variables override config.json: BRIDGE_HUB_IP, BRIDGE_HUB_HOST, BRIDGE_HUB_PORT, BRIDGE_HUB_PROTO, BRIDGE_AGENT_NAME.
node scripts/bridge-client.js health
node scripts/bridge-client.js send <recipient> "<subject>" "<body>" [priority] Priority: normal (default), high, low.
node scripts/bridge-client.js inbox Returns array of pending messages or "Inbox empty."
node scripts/bridge-client.js ack <messageId>
node scripts/bridge-client.js all
node scripts/bridge-client.js files
node scripts/bridge-client.js upload <file-path>
node scripts/bridge-client.js state
Check inbox on every heartbeat or periodic interval: 1. Run: node scripts/bridge-client.js inbox 2. If messages exist → read, process, ack each 3. If high priority → respond immediately or alert human 4. Log activity to daily memory file
const bridge = require('./scripts/bridge-client'); const msgs = await bridge.inbox(); await bridge.send('aristotle', 'Status Update', 'Sprint complete.'); await bridge.ack(msgs[0].id); await bridge.uploadFile('/path/to/file.md');
Sender → POST /api/bridge/message → Hub writes YAML to recipient inbox Recipient polls inbox → GET /api/bridge/inbox/{name} → reads messages Recipient acks → DELETE /api/bridge/inbox/{name}/{id} → message removed
Default family network (customize per deployment): AgentMachineRoleAristotleAlienwareCEO / coordinationDaedalusAlienwareEngineeringThalesAlienwareOperationsSteel ManAlienwareAdversarial reviewResearcherAlienwareIntelligenceEmpiricusnietzsche-i9Testing / validationPlatonietzsche2025Design / implementation
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.