2.6k
GitHub Stars
5
Bundled Files
2 months ago
Catalog Refreshed
3 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill 0x0-messenger- _meta.json280 B
- package-lock.json95.9 KB
- package.json693 B
- README.md4.6 KB
- SKILL.md2.2 KB
Overview
This skill provides peer-to-peer messaging using disposable phone-like numbers and short PINs. It requires no servers or accounts: messages queue for peers, support ephemeral PINs, and enable human approvals and agent-to-agent notifications. Use it to send notifications, perform approval flows, or open temporary inboxes for humans or bots.
How this skill works
The agent runs a local node that exposes a unique 0x0 number and manages short PINs. You create PINs (one-time or persistent) and share a URI; peers connect directly or via queued delivery when offline. Commands let you send messages, open interactive pipes for approvals, listen for inbound events, and host a browser UI for human connection.
When to use it
- Send short, verifiable notifications between systems without central infrastructure
- Request human approval or confirmation in a callable, interactive flow
- Open a temporary public inbox for external users or services
- Coordinate agent-to-agent commands and status messages securely and directly
- Expose a browser or mobile connection for humans without accounts or emails
Best practices
- Use short-lived PINs for one-time approvals and auto-expire when done
- Label PINs clearly to track purpose (e.g., "deploy-approval" or "inbox")
- Queue important messages and confirm delivery with a follow-up read or inbox check
- Revoke PINs immediately after use to prevent reuse or spam
- Use the web UI or QR codes for non-technical human flows to simplify onboarding
Example use cases
- CI sends a P2P message to a developer PIN asking for deploy approval; the developer replies "yes" via mobile and the pipeline continues
- Operations opens a public PIN as a temporary support inbox for an incident; external users submit requests without accounts
- Two agents exchange status updates and commands directly via disposable PINs to avoid central logging
- A scheduled job notifies an on-call engineer through a short-lived PIN and waits for an interactive confirmation
- Create a QR-coded PIN for a field technician to scan and receive secure, ephemeral instructions
FAQ
No. The system is peer-to-peer and relies on locally run nodes and disposable PINs; messages queue for peers if they are offline.
How long do queued messages last?
Queued messages are retained for a limited window (typically 72 hours) to allow delivery when the peer comes online.
Can humans connect from a browser or phone?
Yes. The skill provides a local web UI and supports QR codes and mobile apps so humans can connect without accounts.