Debugging why a mobile OpenClaw node won't pair with its gateway is almost always a mismatch between what the user thinks the network topology is and what the gateway is actually advertising. This skill forces you to declare the intended route first (same machine, LAN, Tailscale, or public URL), then runs the canonical checks to see what the gateway's QR code actually contains. It maps common failure modes like loopback-only binds, missing Tailscale IPs, and stale bootstrap tokens directly to fixes. The approach is opinionated: no guessing from vague error messages, no mixing topologies, and one concrete diagnosis per interaction. If you've ever spent twenty minutes toggling config keys while a phone stubbornly says "can't connect," this will save you.
npx skills add https://github.com/steipete/clawdis --skill node-connect