bridge-twin

Send signed JSONL messages between Buck and Hermes via webhooks.

Updated May 21, 2026
One-click install
npx skills add https://github.com/wahajahmed010/openclaw-skills --skill bridge-twin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bridge-twin
Source: https://github.com/wahajahmed010/openclaw-skills/tree/main/skills/bridge-twin
Command: npx skills add https://github.com/wahajahmed010/openclaw-skills --skill bridge-twin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the problem of unreliable or slow inter-AI messaging by providing a secure, webhook-first JSONL bridge between Buck and Hermes (Brian).

Core Features & Use Cases

  • Send messages to Hermes (Brian): Use signed webhook push with automatic fallback to SSH-triggered inbox reads to ensure delivery.
  • Read and process incoming messages: Retrieve unread JSONL messages from Hermes into Buck’s inbox with optional JSON output or mark-as-read behavior.
  • Test bridge connectivity and health: Verify webhook reachability and endpoint health to troubleshoot connectivity and signature mismatches.

Quick Start

Ask the agent to send Hermes a query by writing the JSON message to Hermes via the webhook bridge:

  • python3 ~/.openclaw/workspace/scripts/bridge_write_hermes.py --type query --payload '{"text":"Hey Brian - status check?"}'

Frequently Asked Questions about bridge-twin

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I send secure webhook notifications between AI agents using HMAC signing?

You can send secure webhook notifications between AI agents by writing JSONL inbox messages and pushing HMAC-SHA256 signed webhooks. This inter-AI messaging bridge uses webhook-first delivery with SSH-triggered fallback reads to ensure reliable message orchestration.

What is JSONL message sequencing for inter-AI communication?

JSONL message sequencing is the process of writing structured line-delimited JSON inbox files to orchestrate command, query, and response communication between AI agents. It ensures messages are retrieved sequentially and supports mark-as-read behavior for tracking unread message states.

How do I test webhook connectivity and endpoint health for automated message orchestration?

You can test webhook connectivity and endpoint health by triggering a health check that verifies webhook reachability and validates HMAC-SHA256 signatures. This troubleshooting step identifies connectivity failures and signature mismatches before sending full query payloads.

Does inter-AI messaging require Docker, or are there docker-agnostic automation tools available?

Inter-AI messaging does not require Docker because this automation tooling is docker-agnostic. It relies on JSONL inbox files, HMAC-SHA256 webhook signatures, and SSH-triggered reads to orchestrate message delivery independently of containerized environments.

Why does my webhook bridge fail to deliver messages when the receiver endpoint is unreachable?

A webhook bridge fails to deliver messages when endpoint health checks detect reachability issues or HMAC signature mismatches. In these cases, the bridge applies fallback behavior through SSH-triggered inbox reads to retrieve unread JSONL messages and ensure delivery.

Can I use webhook automation tooling to retrieve unread JSONL messages with optional JSON output?

Yes, webhook automation tooling can retrieve unread JSONL messages from an inbox file while providing optional JSON output or mark-as-read behavior. This allows you to process incoming queries and responses securely between AI agents.