clawpilot-pair（爪式飞行员对）

ClawPilot Pair

Use this skill for PocketClaw pairing and first-time host setup.

When To Use

Use this skill when the user wants any of the following:

• Pair PocketClaw with the current host
• Install or upgrade clawpilot
• Check whether the host is ready for pairing
• Generate a new pairing code

Do not use this skill for normal chat replies, file delivery, or general diagnostics unrelated to pairing.

Required Workflow

Follow this order exactly. Do not skip checks.

1. Install or upgrade ClawPilot:

npm install -g @rethinkingstudio/clawpilot@latest

1. Determine the target runtime.

• Use openclaw or hermes.
• If the user does not specify and the host only has one runtime, use that runtime.
• If both runtimes are available and the user did not specify, ask which runtime to pair.

1. Run runtime-specific readiness checks before pairing.

For openclaw:

• Verify OpenClaw config can be found.
• Verify gateway auth is usable.
• Verify the local gateway is reachable.
• If auth or gateway reachability fails, stop and report the blocking step with the next command or config fix.

For hermes:

• Verify the hermes CLI exists.
• Verify hermes gateway status works.
• If the gateway service is not installed, tell the user to run:

hermes gateway install
hermes gateway start

• If Hermes API readiness fails, report the exact blocking step and the next command to run.

1. Only after readiness checks pass, generate the pairing code:

clawpilot pair --runtime openclaw

or

clawpilot pair --runtime hermes

Notes:

• clawpilot pair --runtime hermes will prepare the local Hermes API automatically if possible.
• Use --code-only only when the user explicitly wants the code without QR output.

Output Rules

• If successful, put the final pairing code on its own line.
• Keep explanations brief and action-oriented.
• If blocked, say what failed, what was checked, and the next command or config change needed.

Do Not

• Do not invent ClawPilot flags or unsupported commands.
• Do not skip runtime readiness checks and jump straight to pairing.
• Do not return a vague failure such as "configuration error" without naming the missing item.
• Do not force OpenClaw-specific checks when the user is pairing Hermes.
• Do not modify unrelated host settings.