Agent skill · Security

node-connect

Diagnose OpenClaw Android, iOS, or macOS node pairing, QR/setup code, route, auth, and connection failures.

Health-Yanggithub.com/Health-YangGitHub ↗
claude-codeNOASSERTION
Install
npx skills add Health-Yang/MineEcho --skill node-connect --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: vendor/openclaw-gateway/skills/node-connect/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 248
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Node Connect Goal: find the one real route from node -> gateway, verify OpenClaw is advertising that route, then fix pairing/auth. ## Topology first Decide which case you are in before proposing fixes: - same machine / emulator / USB tunnel - same LAN / local Wi-Fi - same Tailscale tailnet - public URL / reverse proxy Do not mix them. - Local Wi-Fi problem: do not switch to Tailscale unless remote access is actually needed. - VPS / remote gateway problem: do not keep debugging `localhost` or LAN IPs. ## If ambiguous, ask first If the setup is unclear or the failure report is vague, ask short clarifying questions before diagnosing. Ask for: - which route they intend: same machine, same LAN, Tailscale tailnet, or public URL - whether they used QR/setup code or manual host/port - the exact app text/status/error, quoted exactly if possible - whether `openclaw devices list` shows a pending pairing request Do not guess from `can't connect`. ## Canonical checks Prefer `openclaw qr --json`. It uses the same setup-code payload Android scans. ```bash openclaw config get gateway.mode openclaw config get gateway.bind openclaw config get gateway.tailscale.mode openclaw config get gateway.remo

What's inside
Steps it walks through
  1. Topology first
  2. If ambiguous, ask first
  3. Canonical checks
  4. Read the result, not guesses
  5. Root-cause map
  6. Fast heuristics
  7. Fix style
Commands it runs
openclaw config get gateway.mode
openclaw config get gateway.bind
openclaw config get gateway.tailscale.mode
openclaw config get gateway.remote.url
openclaw config get gateway.auth.mode
openclaw config get gateway.auth.allowTailscale
openclaw config get plugins.entries.device-pair.config.publicUrl
openclaw qr --json
openclaw devices list
openclaw nodes status
More from MineEcho
All skills →
About this skill
What does the node-connect skill do?

Diagnose OpenClaw Android, iOS, or macOS node pairing, QR/setup code, route, auth, and connection failures.

How do I install it?

Run `npx skills add Health-Yang/MineEcho --skill node-connect --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From Health-Yang/MineEcho, a repository with 248 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going