openclaw-bridge

Translate Windows-side Claude Code requests into OpenClaw multi-agent commands with tier routing.

1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/williamsforeal/Cyclone-SS --skill openclaw-bridge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-bridge
Source: https://github.com/williamsforeal/Cyclone-SS/tree/main/global-skills/openclaw-bridge
Command: npx skills add https://github.com/williamsforeal/Cyclone-SS --skill openclaw-bridge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the confusion and delays of manually figuring out which OpenClaw agent and workspace should handle a request, so Windows-side Claude Code instructions get routed correctly in a 3-tier architecture.

Core Features & Use Cases

  • Intelligent agent routing (PC / Laptop / Cloud): Sends work to the correct agent based on the user’s intent (e.g., builds, creative, infrastructure, data normalization, scraping, cross-node relay, or heartbeat checks).
  • Operational health & heartbeat monitoring: Detects stale agent liveness signals and escalates unresponsive agents to the user/operator.
  • Workspace file sync & task framing: Coordinates file synchronization between agent workspaces and the Cyclone-SS repo, without overwriting operator-defined identity/safety files.
  • WAT framework interpretation (Workflows, Agents, Tools): Ensures requests are handled as probabilistic workflow/agent coordination while deterministic execution happens only via tools.

Example: When a user says “use OpenClaw to trigger the Linux scraping agent, then sync the parsed results back to this repo,” the bridge identifies the scraping-to-normalization pipeline and routes it through Pulse → Hunt → Parse → Relay while maintaining health checks and workspace sync.

Quick Start

Tell your assistant: "Use OpenClaw to route my request to the correct agent, check agent heartbeat if needed, and sync the resulting workspace files back into the Cyclone-SS repo."

Frequently Asked Questions about openclaw-bridge

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

FAQPage Schema
How do I route requests to specific agents in a multi-agent architecture?

Multi-agent architecture request routing translates Windows-side Claude Code instructions into correctly targeted commands for PC, Laptop, and Cloud tiers based on user intent like builds, scraping, or infrastructure tasks.

What is the best way to monitor agent heartbeat and liveness across cloud and local nodes?

Agent heartbeat monitoring detects stale liveness signals across operational tiers and automatically escalates unresponsive agents to the operator to maintain multi-agent architecture health.

How do I synchronize agent workspaces with my repository without overwriting safety files?

Workspace file sync coordinates data transfer between agent workspaces and the Cyclone-SS repo without destructive rsync by default, preserving operator-defined identity and safety files.

Can I use WAT framework workflows to coordinate probabilistic agent tasks?

WAT framework interpretation handles requests as probabilistic workflow and agent coordination, ensuring deterministic execution occurs only through integrated tools within the multi-agent architecture.

Does multi-agent routing support tier-appropriate task decomposition for cross-node relays?

Tier-appropriate task decomposition splits requests across PC, Laptop, and Cloud tiers, correctly routing cross-node relay pipelines such as scraping-to-normalization through designated agents.

Why does my agent routing fail when syncing parsed results back to the repo?

Agent routing and workspace sync failures often stem from unresponsive agents failing heartbeat checks or attempting destructive rsync operations that overwrite protected Cyclone-SS repo files.