clawdentity 0.0.1 → 0.0.2

package/package.json

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

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

@@ -38,8 +38,9 @@ Use this skill when any of the following are requested:
 
 ## Invite Input Assumption
 
-Provide a valid invite code string before running this skill.
-Invite creation is outside this skill scope; this skill focuses on setup, pairing, and relay validation.
+Invite creation is outside this skill scope. This skill consumes two invite types:
+- Registry onboarding invite code (`clw_inv_...`) to obtain PAT when local API key is missing.
+- OpenClaw peer relay invite code (`clawd1_...`) for `openclaw setup`.
 
 ## Human + Agent Flow (strict user-style)
 
@@ -63,12 +64,16 @@ Use these commands as the default execution path for skill utilization:
   - or set env before init: `CLAWDENTITY_REGISTRY=<registry-url>` (supports env-based first-run override)
 - Configure registry URL and API key when missing:
   - `clawdentity config set registryUrl <registry-url>`
+- Complete registry onboarding when API key is missing:
+  - `clawdentity invite redeem <registry-invite-code>`
+  - `clawdentity invite redeem <registry-invite-code> --registry-url <registry-url>`
+- Configure API key only for non-invite fallback:
   - `clawdentity config set apiKey <api-key>`
 - Create and inspect local OpenClaw agent identity:
   - `clawdentity agent create <agent-name> --framework openclaw`
   - `clawdentity agent inspect <agent-name>`
 - Apply OpenClaw invite setup:
-  - `clawdentity openclaw setup <agent-name> --invite-code <invite-code>`
+  - `clawdentity openclaw setup <agent-name> --invite-code <peer-relay-invite-code>`
 - Start connector runtime for relay handoff:
   - `clawdentity connector start <agent-name>`
 - Optional persistent connector autostart:
@@ -92,7 +97,10 @@ Successful confirm establishes mutual trust for the two agent DIDs. After confir
 
 1. Confirm prerequisites with the human.
 - Confirm `clawdentity` CLI is installed and runnable.
-- Confirm API key exists for this agent (if missing, ask the human for it).
+- Confirm local agent name.
+- Confirm OpenClaw peer relay invite code (`clawd1_...`).
+- If API key is missing, request registry onboarding invite code (`clw_inv_...`) first.
+- Only ask for API key when neither local API key nor registry onboarding invite code is available.
 - Confirm OpenClaw state directory path if non-default.
 - Confirm OpenClaw base URL if local endpoint is non-default.
 
@@ -100,24 +108,31 @@ Successful confirm establishes mutual trust for the two agent DIDs. After confir
 - Ensure `~/.openclaw/workspace/skills/clawdentity-openclaw-relay/relay-to-peer.mjs` exists.
 - If missing, install/update skill package contents before setup.
 
-3. Configure local Clawdentity identity for this OpenClaw agent.
+3. Initialize local Clawdentity config.
 - Run `clawdentity config init`.
-- If needed, ask the human for API key and run `clawdentity config set apiKey <key>`.
+- Use `clawdentity config init --registry-url <registry-url>` when registry URL override is required.
+
+4. Complete registry onboarding auth before agent creation.
+- If API key already exists, continue.
+- Else redeem registry onboarding invite:
+  - `clawdentity invite redeem <registry-invite-code>`
+  - optional: `--registry-url <registry-url>`
+- If registry invite code is unavailable, fallback to API key path:
+  - ask human for API key
+  - run `clawdentity config set apiKey <api-key>`
+
+5. Configure local Clawdentity identity for this OpenClaw agent.
 - Create identity: `clawdentity agent create <agent-name> --framework openclaw`.
 - Verify identity: `clawdentity agent inspect <agent-name>`.
 
-4. Ask the human for invite code.
-- Prompt exactly for one invite code string.
-- Do not ask for DID/proxy URL when invite code is present.
-
-5. Run automated setup from invite code.
+6. Run automated setup from peer relay invite code.
 - Execute:
-  `clawdentity openclaw setup <agent-name> --invite-code <invite-code>`
+  `clawdentity openclaw setup <agent-name> --invite-code <peer-relay-invite-code>`
 - Use `--openclaw-dir <path>` when state directory is non-default.
 - Use `--openclaw-base-url <url>` when local OpenClaw HTTP endpoint is non-default.
 - Use `--peer-alias <alias>` only when alias override is required.
 
-6. Verify setup outputs.
+7. Verify setup outputs.
 - Confirm setup reports:
   - peer alias
   - peer DID
@@ -127,17 +142,17 @@ Successful confirm establishes mutual trust for the two agent DIDs. After confir
   - relay runtime config path
 - Confirm `~/.clawdentity/openclaw-agent-name` is set to the local agent name.
 
-7. Start connector runtime for local relay handoff.
+8. Start connector runtime for local relay handoff.
 - Run `clawdentity connector start <agent-name>`.
 - Optional: run `clawdentity connector service install <agent-name>` for persistent autostart.
 
-8. Complete trust pairing bootstrap.
+9. Complete trust pairing bootstrap.
 - Run pairing start (`POST /pair/start`) from the owner/initiator side.
 - Share returned one-time `pairingCode` with responder side.
 - Run pairing confirm (`POST /pair/confirm`) from responder side.
 - Confirm pairing success before relay test.
 
-9. Validate with user-style relay test.
+10. Validate with user-style relay test.
 - Run `clawdentity openclaw doctor` to verify setup health and remediation hints.
 - Run `clawdentity openclaw relay test --peer <alias>` to execute a probe.
 - Confirm probe success and connector-mediated delivery logs.
@@ -146,10 +161,12 @@ Successful confirm establishes mutual trust for the two agent DIDs. After confir
 ## Required question policy
 
 Ask the human only when required inputs are missing:
-- Missing Clawdentity API key.
+- Missing local agent name.
+- Missing peer relay invite code (`clawd1_...`).
+- Missing registry onboarding invite code (`clw_inv_...`) when API key is absent.
+- Missing Clawdentity API key only when registry onboarding invite code is unavailable.
 - Unclear OpenClaw state directory.
 - Non-default OpenClaw base URL.
-- Missing invite code.
 - Local connector runtime or peer network route is unknown or unreachable from agent runtime.
 
 ## Failure Handling
@@ -160,7 +177,7 @@ If setup or relay fails:
 - Ensure connector runtime is active (`clawdentity connector start <agent-name>`).
 - Re-run `clawdentity openclaw doctor`.
 - Re-run `clawdentity openclaw relay test --peer <alias>`.
-- Re-run the same user-style flow from step 5 onward only after health checks pass.
+- Re-run the same user-style flow from step 6 onward only after health checks pass.
 
 ## Bundled Resources