Node Connect
技能 已验证 活跃Diagnose 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.
功能
- 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
使用场景
- 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.
非目标
- Setting up OpenClaw from scratch.
- Configuring general network infrastructure beyond what's needed for OpenClaw.
- Resolving issues unrelated to OpenClaw node connectivity.
工作流
- 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.
先决条件
- OpenClaw CLI installed
- Tailscale CLI installed (if applicable)
- Access to OpenClaw gateway configuration
安装
npx skills add steipete/clawdis通过 npx 运行 Vercel skills CLI(skills.sh)— 需要本地安装 Node.js,以及至少一个兼容 skills 的智能体(Claude Code、Cursor、Codex 等)。前提是仓库遵循 agentskills.io 格式。
质量评分
已验证类似扩展
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
100使用 Chrome DevTools MCP 和文档来排查连接和目标问题。当 list_pages、new_page 或 navigate_page 失败,或服务器初始化失败时,触发此技能。
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