Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
Fix display name
What This Skill Does
Sends and receives P2P messages using disposable PINs tied to numeric identities. No accounts, servers, or infrastructure required. Supports one-time, expiring, and public PINs for temporary or ongoing channels.
Unlike webhook or messaging APIs, it requires no account signup, server setup, or persistent infrastructure, so any script or agent can communicate ad-hoc with a single CLI command.
When to use it
- Requesting human approval before a destructive deployment step
- Passing build status between isolated CI agents
- Creating a one-use PIN for a contractor to submit credentials
- Setting up a temporary inbox for a short-lived automation workflow
- Chaining agent handoffs where each step signals the next via message
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: wait for a human to approve deployment to production
- 1Run `c0x0 pin new --once --label deploy-approval` to create a one-time PIN
- 2Send the PIN address to the human operator out-of-band
- 3Run `c0x0 pipe <peer> <pin>` and emit a JSON message asking for yes/no confirmation
- 4Listen for incoming JSON response with `type: message`
- 5Check content for approval, then run `c0x0 pin revoke <pin>` and proceed or abort
Deployment proceeds if response content is "yes", otherwise the agent halts and reports the rejection
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.