What problem does it solve? Mobile and desktop nodes fail to connect to an OpenClaw gateway for many reasons—loopback-only binding, wrong network route, expired setup codes, or unapproved pairing requests—and vague errors like "can't connect" make root causes hard to find. ## Core Features & Use Cases - Topology-First Diagnosis: Classifies the setup as same machine, same LAN, Tailscale tailnet, or public URL before proposing fixes, avoiding mixed-up solutions. - Canonical Config Checks: Uses openclaw qr --json, openclaw config get, and openclaw devices list to read the actual advertised gateway route instead of guessing. - Root-Cause Mapping: Maps specific errors (loopback-only gateway, invalid bootstrap token, unauthorized, pairing required) to concrete fixes like enabling Tailscale Serve or approving pending devices. - Use Case: A user scans a QR code on their Android phone but the app says "bootstrap token invalid or expired"—the Skill identifies the stale setup code, fixes the advertised route, and walks through regenerating the code and approving the device. ## Quick Start Diagnose why my OpenClaw Android app cannot connect to my gateway and tell me the exact fix.