node-connect Skill
Diagnose OpenClaw Control UI browser and native Android, iOS, or macOS node connection failures across route, auth, pairing, QR/setup-code, and reconnect states. Published by openclaw in openclaw.
Decision snapshot
Is this a fit?
Browser automation, Deployment, Design and media, Includes SKILL.md
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
23 days ago · NOASSERTION license
No specific cautions were detected. Review the source and requested permissions before installing.
What is node-connect Skill?
Diagnose OpenClaw Control UI browser and native Android, iOS, or macOS node connection failures across route, auth, pairing, QR/setup-code, and reconnect states. Published by openclaw in openclaw. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Browser automation
- Deployment
- Design and media
- Browser automation use cases
- Deployment use cases
Declared skill metadata
- Source file: skills/node-connect/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use node-connect Skill
- Use it for browser automation.
- Use it for deployment.
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: openclaw
- Repository: openclaw/openclaw
- Skill file: skills/node-connect/SKILL.md
What it does
Diagnose OpenClaw Control UI browser and native Android, iOS, or macOS node connection failures across route, auth, pairing, QR/setup-code, and reconnect states.
Skill instructions
Node Connect Goal: fix one exact client against one exact Gateway, then prove that client's fresh connection. 1. Lock the target Record the target environment/profile, OpenClaw binary, config/state root, Gateway URL/port, and service before changing anything. - Use the named deployment wrapper/profile for every config, log, service, device, and node command. - Never drift to a bare openclaw, proof environment, or similarly named deployment. - If the global executable is stale, invoke the target through its owner. - Verify status, config, logs, and process identity describe the same Gateway. Do not mutate pairing or auth until the target is unambiguous. 2. Classify the client Classify from the request and Gateway log before choosing commands: - Control UI browser: the user says browser, dashboard, Control UI, or webchat; logs show client=openclaw-control-ui or mode=webchat. - Native mobile/node: the official app shows Connect, Scan QR, or setup code; logs/request metadata show a native
Verified compatibility and discovery
Frequently asked questions
What is node-connect?
node-connect is a open-source AI agent skill with Copy skill directory. Diagnose OpenClaw Control UI browser and native Android, iOS, or macOS node connection failures across route, auth, pairing, QR/setup-code, and reconnect states.
Who is node-connect best for?
node-connect is best for reusing agent instructions, scripts, and references, browser automation workflows, deployment workflows, design and media workflows.
How do I install node-connect?
Install or run node-connect using Copy skill directory. Check node-connect for the latest setup command.
Is node-connect actively maintained?
node-connect may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
