Claude MarketplacesSubmit
steipete avatar

Node Connect

steipete/clawdis

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.

skills.sh installs
253
GitHub stars
376.2K
last updated
Jun 3, 2026
View on GitHub

Install

$ npx -y skills add steipete/clawdis --skill node-connect --agent claude-code

Installs into .claude/skills of the current project.

Files

Node Connect

Goal: fix one exact client against one exact Gateway, then prove that client's fresh connection.

1. Lock the target

Record the target environment/profile, OpenClaw binary, config/state root, Gateway URL/port, and service before changing anything.

  • Use the named deployment wrapper/profile for every config, log, service, device, and node command.
  • Never drift to a bare openclaw, proof environment, or similarly named deployment.
  • If the global executable is stale, invoke the target through its owner.
  • Verify status, config, logs, and process identity describe the same Gateway.

Identify the target Gateway before changing pairing or auth.

2. Classify the client

Classify from the request and Gateway log before choosing commands:

  • Control UI browser: the user says browser, dashboard, Control UI, or webchat; logs show client=openclaw-control-ui or mode=webchat.
  • Native mobile/node: the official app shows Connect, Scan QR, or setup code; logs/request metadata show a native client or role=node.

A phone can be either client. Do not use openclaw qr or openclaw nodes status for a phone browser; those belong to native mobile/node pairing.

SKILL.md on GitHub

Sponsors

Promote your product hereReach 125k+ visitors monthlyPromote your product hereReach 125k+ visitors monthlyAgent CaffeineSponsoredClose your lid, come back to finished workSnugSponsoredThe clipboard manager for the AI eraPromote your product hereReach 125k+ visitors monthlyWaxSponsoredBlock anything with supervision, without erasing your iPhonePromote your product hereReach 125k+ visitors monthlyknobsSponsoredSee your site on any phone, any day, in any language

Details

Repository
github.com/steipete/clawdis
First seen
Jun 3, 2026

More from steipete/clawdis

All 61

Recommended

1juliusbrussee avatarcavemanjuliusbrussee/cavemanUltra-compressed communication mode. Cuts output tokens 65% (measured) by speaking like caveman while keeping full technical accuracy. Supports intensity levels618.3Kskills.sh installs
2mattpocock avatargrill-memattpocock/skillsA relentless interview to sharpen a plan or design.1.5Mskills.sh installs
3shadcn avatarimproveshadcn/improveSurvey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on s40Kskills.sh installs
4obra avatarsystematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes326.7Kskills.sh installs
5forrestchang avatarkarpathy-guidelinesforrestchang/andrej-karpathy-skillsBehavioral guidelines to reduce common LLM coding mistakes through explicit assumptions, simplicity, and verifiable success criteria.17.9Kskills.sh installs
6vercel-labs avatarfind-skillsvercel-labs/skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express int4.3Mskills.sh installs