Node Connect

Skill Verified Active

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

Purpose

To quickly diagnose and resolve OpenClaw node connection and pairing failures by providing expert guidance on common issues and network configurations.

Features

Diagnose OpenClaw node pairing failures
Troubleshoot QR/setup code issues
Identify routing and connection problems
Resolve authentication failures
Support for Android, iOS, and macOS platforms

Use Cases

When an Android, iOS, or macOS device fails to connect to the OpenClaw gateway.
When encountering issues with OpenClaw QR or setup codes.
To debug network routing or authentication problems between OpenClaw nodes.
To pinpoint the exact cause of connection failures for OpenClaw.

Non-Goals

Setting up OpenClaw from scratch.
Configuring general network infrastructure beyond what's needed for OpenClaw.
Resolving issues unrelated to OpenClaw node connectivity.

Workflow

Identify the intended network route (same machine, LAN, Tailscale, public URL).
Ask clarifying questions if the setup is ambiguous.
Execute canonical diagnostic commands (`openclaw qr --json`, `openclaw devices list`, etc.).
Analyze command output to determine the root cause.
Provide a concrete diagnosis and a specific route or fix.

Prerequisites

OpenClaw CLI installed
Tailscale CLI installed (if applicable)
Access to OpenClaw gateway configuration

Installation

npx skills add steipete/clawdis

Runs the Vercel skills CLI (skills.sh) via npx — needs Node.js locally and at least one installed skills-compatible agent (Claude Code, Cursor, Codex, …). Assumes the repo follows the agentskills.io format.

Quality Score

Verified

100 /100

Analyzed about 12 hours ago

Trust Signals

Last commitabout 12 hours ago

GitHub owner steipete

Stars371.6k

Downloads 4.6M

LicenseMIT

Websiteopenclaw.ai

Status

View Source

Similar Extensions

Openclaw Debugging

100

Debug OpenClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before changing code.

Skill

steipete

Systematic Debugging

100

Systematic debugging methodology emphasizing root cause analysis over quick fixes

Skill

bobmatnyc

Troubleshooting

100

Uses Chrome DevTools MCP and documentation to troubleshoot connection and target issues. Trigger this skill when list_pages, new_page, or navigate_page fail, or when the server initialization fails.

Skill

ChromeDevTools

Crash Analytics

When the user wants to monitor, triage, or reduce their app's crash rate — including setting up Crashlytics, prioritizing which crashes to fix first, interpreting crash data, and understanding how crashes affect App Store ranking. Use when the user mentions "crash", "crashlytics", "crash rate", "ANR", "app not responding", "crash-free sessions", "crash-free users", "symbolication", "stability", "firebase crashes", "app crashing", or "crash report". For overall analytics setup, see app-analytics.

Skill

Eronred

App Icon Optimization

When the user wants to design, test, or improve their app icon to increase tap-through rate and conversions in App Store search and browse. Use when the user mentions "app icon", "icon design", "icon A/B test", "icon variants", "tap-through rate", "icon conversion", "icon refresh", or wants to know what makes a good app icon. For screenshot optimization, see screenshot-optimization. For full listing A/B tests, see ab-test-store-listing.

Skill

Eronred

Root Cause Tracing

Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior

Skill

NeoLabHQ