$ ~/registry/skill/openclaw-node-connect

SKILL

node-connect

Name: node-connect
Author: openclaw

Diagnose OpenClaw node pairing, auth, routing, and connection issues.

Stars

★ 382,582

Source

GitHub

Updated

2026-07-11

// securityCaution

Prompt only, no code
Open source
Community-trusted· 377.5k

Summary

The material indicates this is essentially a prompt/documentation-style skill for diagnosing OpenClaw node connectivity, with no declared secrets, remote endpoints, or built-in execution/egress logic. Given the open-source source and very strong community adoption, overall risk is low, though it does instruct users to run local diagnostic commands and expose local config/status details, so minimal disclosure is still advisable.

CredentialsLow risk

The material explicitly states no keys or environment variables are required, and the README does not request tokens, API keys, or account credentials; it focuses on pairing/auth diagnostics without direct signs of credential collection or misuse.

Network egressLow risk

No remote endpoints are declared, and the skill is marked prompt-only; the document discusses the user's existing OpenClaw/Tailscale/public routing rather than the skill itself sending data to third parties, with no standalone data-egress red flags observed.

Code executionCaution

The README explicitly recommends running multiple local commands such as openclaw config/qr/devices/nodes and tailscale status; this is typical for diagnostic tooling but does involve local CLI execution, so caution is appropriate.

Data accessCaution

The document involves reading local OpenClaw configuration, device pairing status, node status, and possibly Tailscale status output; it does not appear to request broad arbitrary file access or excessive system privileges, but it does touch local runtime and network configuration data.

Supply chainLow risk

The source is an open-source GitHub repository, and the system flags it as open-source with extremely high community adoption (~377k stars), which are strong risk-reducing signals; while the license and maintenance status are unclear, the available material shows no closed-source, abandoned, or suspicious distribution red flags.

Recommendations

Run the README diagnostic commands only on trusted machines, and avoid exposing full configs, QR contents, or device status to unrelated parties.
Before sharing command output, check for host addresses, pairing details, or internal network topology and redact as needed.
For commands that imply approval actions or configuration changes, review side effects manually instead of copy-pasting blindly.
Verify recent commits, issue responses, and release history to confirm current maintenance activity.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "node-connect" skill from askskill:
1. Download https://raw.githubusercontent.com/openclaw/openclaw/main/skills/node-connect/SKILL.md
2. Save it as ~/.claude/skills/node-connect/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// examples

Troubleshoot QR pairing failure

Prompt

Help me diagnose an OpenClaw Android node QR pairing failure. I scanned the QR code, but the device says pairing cannot be completed. Please check whether the QR code expired, whether the setup code matches, whether the node is reachable, and list common fixes step by step.

Expected

A step-by-step troubleshooting checklist with likely causes and fixes.

Analyze auth and connection errors

Prompt

I am seeing authentication failures and connection drops when connecting to an OpenClaw macOS node. Please help me determine whether this is caused by bad credentials, permission issues, network routing problems, or node health issues, and provide ways to verify each possibility.

Expected

A categorized diagnosis by issue type, with verification steps and recommended actions.

Check cross-platform node connectivity

Prompt

Help me check connectivity issues between OpenClaw iOS and Android nodes. Focus on routing configuration, node discovery, network restrictions, and handshake failures, and provide a prioritized troubleshooting order.

Expected

A prioritized troubleshooting flow covering routing, discovery, network, and handshake stages.

// docs

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.

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

If this OpenClaw instance is pointed at a remote gateway, also run:

openclaw qr --remote --json

If Tailscale is part of the story:

tailscale status --json

Read the result, not guesses

openclaw qr --json success means:

gatewayUrl: this is the actual endpoint the app should use.
urlSource: this tells you which config path won.

Common good sources:

gateway.bind=lan: same Wi-Fi / LAN only
gateway.bind=tailnet: direct tailnet access
gateway.tailscale.mode=serve or gateway.tailscale.mode=funnel: Tailscale route
plugins.entries.device-pair.config.publicUrl: explicit public/reverse-proxy route
gateway.remote.url: remote gateway route

Root-cause map

If openclaw qr --json says Gateway is only bound to loopback:

remote node cannot connect yet
fix the route, then generate a fresh setup code
gateway.bind=auto is not enough if the effective QR route is still loopback
same LAN: use gateway.bind=lan
same tailnet: prefer gateway.tailscale.mode=serve or use gateway.bind=tailnet
public internet: set a real plugins.entries.device-pair.config.publicUrl or gateway.remote.url

If gateway.bind=tailnet set, but no tailnet IP was found:

gateway host is not actually on Tailscale

If qr --remote requires gateway.remote.url:

remote-mode config is incomplete

If the app says pairing required:

network route and auth worked
approve the pending device

openclaw devices list
openclaw devices approve --latest   # preview only; copy the requestId from output
openclaw devices approve <requestId>

If the app says bootstrap token invalid or expired:

old setup code
generate a fresh one and rescan
do this after any URL/auth fix too

If the app says unauthorized:

wrong token/password, or wrong Tailscale expectation
for Tailscale Serve, gateway.auth.allowTailscale must match the intended flow
otherwise use explicit token/password

Fast heuristics

Same Wi-Fi setup + gateway advertises 127.0.0.1, localhost, or loopback-only config: wrong.
Remote setup + setup/manual uses private LAN IP: wrong.
Tailnet setup + gateway advertises LAN IP instead of MagicDNS / tailnet route: wrong.
Public URL set but QR still advertises something else: inspect urlSource; config is not what you think.
openclaw devices list shows pending requests: stop changing network config and approve first.