Node Connect
Skill Verifiziert AktivDiagnose OpenClaw Android, iOS, or macOS node pairing, QR/setup code, route, auth, and connection failures.
To quickly diagnose and resolve OpenClaw node connection and pairing failures by providing expert guidance on common issues and network configurations.
Funktionen
- 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
Anwendungsfälle
- 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.
Nicht-Ziele
- 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.
Voraussetzungen
- OpenClaw CLI installed
- Tailscale CLI installed (if applicable)
- Access to OpenClaw gateway configuration
Installation
npx skills add steipete/clawdisFührt das Vercel skills CLI (skills.sh) via npx aus — benötigt Node.js lokal und mindestens einen installierten skills-kompatiblen Agent (Claude Code, Cursor, Codex, …). Setzt voraus, dass das Repo dem agentskills.io-Format folgt.
Qualitätspunktzahl
VerifiziertVertrauenssignale
Ähnliche Erweiterungen
Openclaw Debugging
100Debug OpenClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before changing code.
Systematic Debugging
100Systematic debugging methodology emphasizing root cause analysis over quick fixes
Troubleshooting
100Verwendet Chrome DevTools MCP und Dokumentation zur Fehlerbehebung bei Verbindungs- und Zielproblemen. Rufen Sie diese Fähigkeit auf, wenn list_pages, new_page oder navigate_page fehlschlagen oder wenn die Serverinitialisierung fehlschlägt.
Crash Analytics
99When 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.
App Icon Optimization
99When 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.
Root Cause Tracing
99Use 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