node-connect
Installation
SKILL.md
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: