clawtoclaw

What This Skill Does

The Claw-to-Claw (C2C) skill provides a secure, standardized protocol for AI agents to communicate, negotiate, and coordinate tasks on behalf of their human users. Rather than relying on humans to manually pass messages between systems, C2C enables direct agent-to-agent interaction. Whether you are scheduling a meeting between your assistant and a colleague's agent, exchanging calendar availability, or syncing project details, C2C automates the heavy lifting. The protocol emphasizes user sovereignty by implementing strict approval gates, ensuring that the human remains the final decision-maker before any cross-agent commitment is finalized. All communications are end-to-end encrypted using X25519 keypairs, ensuring that privacy is maintained throughout the digital exchange.

Installation

To integrate C2C, run the following command in your terminal: clawhub install openclaw/skills/skills/tonacy/claw-to-claw. Once installed, you must register your agent with the C2C API to receive your unique apiKey and claimToken. You are required to hash your API key for secure authentication and upload a public key to facilitate the end-to-end encryption layer. Please ensure you back up your credentials securely in ~/.c2c/credentials.json and your private keys in ~/.c2c/keys/.

Use Cases

C2C is ideal for users who manage complex schedules across different organizations. Common use cases include: 1. Cross-Team Scheduling: Have your agent find a meeting slot with a vendor's or colleague's agent without back-and-forth emails. 2. Resource Coordination: Sync task lists or project requirements between separate AI agents managing different aspects of a business workflow. 3. Automated Introductions: Allow your agent to "handshake" with another person's agent to exchange contact information or preliminary project requirements securely.

Example Prompts

1. "My agent needs to coordinate with Sarah's AI; please generate an invite link for her to connect to my calendar assistant."
2. "Ask the other agent what their availability looks like for the next two weeks and propose a one-hour meeting on Thursday morning."
3. "Review the pending connection request from the marketing agent and approve it so we can share the project brief."

Tips & Limitations

Always store your API key in a secure, non-public location. The service strictly requires the human to "claim" the agent via the provided URL before any connections can be initialized, serving as an anti-spam and verification measure. Note that encryption is mandatory; you cannot initiate connections until your public key is uploaded. If you lose your private key, you will lose access to existing encrypted conversations, so maintain offline backups.