ocb-bridge

Onboard OpenClaw agents to the OpenClaw Bridge and verify bidirectional messaging.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/gevrey/openclaw_backup --skill ocb-bridge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ocb-bridge
Source: https://github.com/gevrey/openclaw_backup/tree/main/skills/ocb-bridge
Command: npx skills add https://github.com/gevrey/openclaw_backup --skill ocb-bridge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Operate the OpenClaw Bridge (OCB) for multi-agent communication. Use when asked to onboard a new OpenClaw agent to OCB, verify bidirectional delivery, troubleshoot message routing/ACK failures, explain why Telegram username resolution fails from client bots, or produce OCB runbooks and handoff documentation.

Core Features & Use Cases

  • Onboard and verify new OpenClaw agent in OCB
  • Validate bidirectional messaging and ACK evidence
  • Troubleshoot message routing failures and username resolution issues
  • Produce OCB runbooks and handoff documentation

Quick Start

Onboard a new agent to OCB and verify bidirectional delivery.

Frequently Asked Questions about ocb-bridge

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

FAQPage Schema
How do I onboard a new agent to the OpenClaw Bridge?

To onboard an agent to the OpenClaw Bridge, you must verify bridge health, confirm SSH access and CLI availability, validate client artifacts, and register the agent in the bridge registry to establish connectivity.

Why does Telegram username resolution fail from client bots in OpenClaw?

Telegram username resolution from client bots fails when OpenClaw Bridge connectivity is misconfigured, requiring you to verify bridge health and validate bidirectional messaging to resolve the routing issue.

How do I verify bidirectional messaging and ACK evidence in OCB?

Verifying bidirectional messaging in OCB requires checking ACK evidence and confirming that the agent is properly registered in the bridge registry after validating basic bridge health and CLI availability.

What is needed to produce OCB runbooks and handoff documentation?

Producing OCB runbooks and handoff documentation requires documenting the troubleshooting steps for message routing, ACK failures, and the bridge registry registration process used during agent onboarding.

What are the requirements for establishing OpenClaw Bridge connectivity across agent deployments?

Establishing OpenClaw Bridge connectivity requires verifying bridge health, ensuring SSH access, confirming CLI availability, checking client artifacts, and completing proper registration in the bridge registry.