← Back to Skills Marketplace
node-connection-doctor
by
HuoXinJiang
· GitHub ↗
· v1.0.3
· MIT-0
134
Downloads
0
Stars
0
Active Installs
3
Versions
Install in OpenClaw
/install node-connection-doctor
Description
Diagnose and fix OpenClaw node connection issues with automated checks, error-specific solutions, CLI guidance, and optional one-click repairs.
Usage Guidance
Before installing or running this skill: (1) Verify your environment: ensure Node.js and the OpenClaw CLI are present and in PATH — the package does not declare these but the scripts require them. (2) Backup your OpenClaw config directory before running fixes. (3) Use diagnose mode first; avoid auto_confirm/auto-run fix in production. (4) Be aware the fix flow prints bootstrap tokens to stdout — if your system collects console output (logs, monitoring, screenshots), treat these outputs as sensitive and avoid exposing them. (5) Ask the author to correct metadata (declare required binaries, clarify the unnecessary 'system:cron' permission) and to provide a dry-run option that shows exact commands without executing them (diagnose partly does this). (6) If you need stronger assurance, run the scripts in a controlled sandbox or with limited logging, and review the source files locally before executing.
Capability Assessment
Purpose & Capability
The skill's code and docs are aligned with the stated purpose (diagnose and fix OpenClaw node connections). However, the package metadata and SKILL.md do not declare important runtime prerequisites: the scripts invoke the 'openclaw' CLI and require Node.js to run, yet 'required binaries' is empty and the manifest does not state 'openclaw' CLI as required. That mismatch is inconsistent and should be corrected before trusting the skill.
Instruction Scope
Runtime instructions and the scripts stay within troubleshooting scope (gateway status, device-pair config, ping/Tailscale checks, resetting tokens, restarting gateway). Two points to note: (1) the fix workflow prints newly-generated bootstrap tokens to stdout (scripts/fix.js logs 'Token:'), which is useful for a user but sensitive if logs are captured or forwarded; (2) scripts read local configuration files (./config/plugins/entries/device-pair.config.json) and execute shell commands — both are expected for this purpose but may expose secrets/config and should be run carefully.
Install Mechanism
There is no remote install script or third-party download; this is effectively an instruction + script bundle included in the package. That reduces supply-chain risk compared to remote downloads. No install spec is present, so nothing will be automatically fetched from arbitrary URLs.
Credentials
The skill requests no environment variables or external credentials, which is reasonable. But it does require (but does not declare) Node.js and the 'openclaw' CLI in PATH. It also reads local config files that may contain tokens. The code prints bootstrap tokens to stdout — reasonable for local pairing, but this is sensitive and could be captured by logs or monitoring; the SKILL.md/FAQ claim 'does not collect API keys or send configuration to external servers', which is accurate for included code, but the package also contains marketing/docs that refer to Slack/webhook integration (not implemented) and to possible automated publishing workflows that would require credentials — these are out-of-band and should not be conflated with runtime behavior.
Persistence & Privilege
The skill does not request 'always: true' and does not attempt to persist itself or modify other skills. Hook manifest lists permissions 'node:exec' (expected) and 'system:cron' (unused by the provided scripts) — the cron permission is unexpected and unnecessary for the included code and should be questioned. The fix mode can modify OpenClaw configuration and restart services (requires admin/root) which is appropriate for a repair tool but increases impact if misused or run unattended (auto_confirm=true).
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install node-connection-doctor - After installation, invoke the skill by name or use
/node-connection-doctor - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.3
Initial release of node-connection-doctor.
- Diagnose and fix OpenClaw node connection issues automatically.
- Supports common failure scenarios: QR/setup code errors, manual pairing failures, VPN/Tailscale problems, and configuration errors.
- Provides step-by-step CLI suggestions and exports diagnostic reports.
- Includes one-click repair options (reset tokens, rebind/restart gateway).
- English documentation and workflow files added.
v1.0.1
Initial release (English version): diagnose and fix OpenClaw node connection issues
v1.0.0
Initial release: diagnose and fix OpenClaw node connection issues
Metadata
Frequently Asked Questions
What is node-connection-doctor?
Diagnose and fix OpenClaw node connection issues with automated checks, error-specific solutions, CLI guidance, and optional one-click repairs. It is an AI Agent Skill for Claude Code / OpenClaw, with 134 downloads so far.
How do I install node-connection-doctor?
Run "/install node-connection-doctor" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is node-connection-doctor free?
Yes, node-connection-doctor is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does node-connection-doctor support?
node-connection-doctor is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created node-connection-doctor?
It is built and maintained by HuoXinJiang (@huoxinjiang); the current version is v1.0.3.
More Skills