openclaw-availability-utilization

Enforce preflight checks, routing, and failover controls for OpenClaw gateway reliability.

Updated Apr 11, 2026

Search Tags:#routing #failover #availability #preflight #utilization #openclaw

Ready to run

npx skills add https://github.com/chf3198/devenv-ops --skill openclaw-availability-utilization

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openclaw-availability-utilization
Source: https://github.com/chf3198/devenv-ops/tree/main/skills/openclaw-availability-utilization
Command: npx skills add https://github.com/chf3198/devenv-ops --skill openclaw-availability-utilization

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps the OpenClaw gateway reachable and performant by enforcing mandatory preflight checks, routing decisions, and robust failover controls to prevent downtime and underutilization.

Core Features & Use Cases

Mandatory session preflight checks before sessions and at 60–90 minute intervals during long tasks to ensure health and connectivity.
Intelligent task routing to the best fleet lane based on availability, profile, and health signals.
Utilization targets with graceful fallback to cloud or local modes when the primary lane is degraded.
Evidence logging and integration with router and network resource components for observability and auditing.

Quick Start

Run a preflight, route a session, and adapt based on health and utilization signals.

Frequently Asked Questions about openclaw-availability-utilization

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

FAQPage Schema

How do I enforce gateway failover and preflight checks to prevent downtime?▼

Gateway failover and preflight checks are enforced through a session control loop that executes mandatory health validations before routing decisions, ensuring high availability by verifying connectivity before execution and adapting dynamically upon degradation.

How do I route tasks to the best available fleet lane based on health signals?▼

Task routing selects the optimal fleet lane by evaluating real-time availability, profile configurations, and health signals, dynamically directing execution traffic to ensure continuous gateway reliability and performance.

Does the availability control loop work across Windows and Linux environments?▼

The availability control loop operates across both Windows and Linux environments, applying automated health checks, dynamic lane selection, and utilization targets uniformly during coding sessions, deployment planning, and runtime operations.

How often are preflight checks required during long coding or deployment tasks?▼

Preflight checks are mandatory before sessions begin and automatically re-run at 60 to 90 minute intervals during long tasks to continuously verify health, connectivity, and utilization thresholds.

What happens when the primary fleet lane degrades during runtime operations?▼

When the primary lane degrades, the control loop triggers a graceful fallback to cloud or local execution modes based on utilization targets, maintaining session continuity while logging evidence for observability.