clawdentity 0.0.9 → 0.0.10

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "clawdentity",
-  "version": "0.0.9",
+  "version": "0.0.10",
   "type": "module",
   "publishConfig": {
     "access": "public"

package/skill-bundle/openclaw-skill/skill/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: clawdentity_openclaw_relay
 description: This skill should be used when the user asks to install or configure Clawdentity relay for OpenClaw agents and prepare them for pairing and message delivery.
-version: 0.2.0
+version: 0.2.1
 ---
 
 # Clawdentity OpenClaw Relay Skill
 
 This skill prepares a local OpenClaw agent in a strict sequence:
-1. finish registry onboarding and generate/store API key
+1. finish registry onboarding by redeeming an invite (`clw_inv_...`) and store API key
 2. create local agent identity
 3. configure relay runtime
 4. become ready to start or accept QR pairing
@@ -43,9 +43,12 @@ Relay invite codes are not part of this flow.
 ## Inputs
 
 Required for onboarding:
-- Registry onboarding invite code: `clw_inv_...` (or existing local API key)
+- Registry onboarding invite code: `clw_inv_...` (default onboarding path)
 - Local agent name
 
+Optional only for recovery/advanced operator flows:
+- Existing API key (only when user explicitly says no invite is available)
+
 Required for pairing phase (after setup):
 - Pairing QR from the other side (`clwpair1_...` inside QR image)
 
@@ -63,7 +66,8 @@ Required for pairing phase (after setup):
 - `clawdentity config set registryUrl <registry-url>`
 - `clawdentity invite redeem <registry-invite-code>`
 - `clawdentity invite redeem <registry-invite-code> --registry-url <registry-url>`
-- `clawdentity config set apiKey <api-key>` (fallback only when invite is unavailable)
+- `clawdentity config get apiKey`
+- `clawdentity config set apiKey <api-key>` (manual recovery only when user explicitly cannot provide invite)
 - `clawdentity agent create <agent-name> --framework openclaw`
 - `clawdentity agent inspect <agent-name>`
 - `clawdentity openclaw setup <agent-name>`
@@ -84,7 +88,9 @@ Required for pairing phase (after setup):
 - If `--invite-code` appears, treat CLI as outdated and upgrade before continuing:
   - `npm install -g clawdentity@latest`
 - Confirm local agent name.
-- Confirm either existing API key or `clw_inv_...`.
+- Check local API key status with `clawdentity config get apiKey`.
+- If API key is missing, ask for onboarding invite `clw_inv_...` and continue with invite redeem.
+- Do not ask for raw API key unless the user explicitly says invite is unavailable.
 - Confirm OpenClaw path/base URL only if non-default.
 - Do not ask for pairing inputs before onboarding is complete.
 
@@ -97,8 +103,9 @@ Required for pairing phase (after setup):
 - If needed, run with `--registry-url`.
 
 4. Finish onboarding and generate API key.
-- If API key already exists locally, continue.
-- Else run `clawdentity invite redeem <clw_inv_...>`.
+- Preferred path: run `clawdentity invite redeem <clw_inv_...>`.
+- If local API key already exists and user explicitly wants to reuse it, continue without redeem.
+- Use `config set apiKey` only as a manual recovery path when user cannot provide invite.
 - Confirm output shows:
   - `Invite redeemed`
   - API key token printed once
@@ -135,12 +142,14 @@ Required for pairing phase (after setup):
 
 Ask only when missing:
 - local agent name
-- onboarding invite (`clw_inv_...`) when API key is absent
+- onboarding invite (`clw_inv_...`) unless user explicitly requests API-key recovery path
 - non-default OpenClaw path/base URL
 - pairing QR image path for confirm
 
 Do not ask for relay invite codes.
 Do not ask for `clawd1_...` values.
+Do not state that API key is required before invite redeem.
+Do not suggest switching endpoints unless user explicitly asks for endpoint changes.
 
 ## Failure Handling