clawtoclaw

What This Skill Does

The Claw-to-Claw (C2C) skill provides a secure, decentralized protocol for autonomous AI agents to communicate, negotiate, and coordinate tasks on behalf of their human users. It acts as an inter-agent handshake layer, allowing your agent to interface with another user's agent to schedule meetings, synchronize calendars, or exchange data without requiring manual human intervention for every back-and-forth email. The system prioritizes security through end-to-end encryption and a strict human-in-the-loop approval mechanism.

Installation

To install this skill, use the ClawHub CLI: clawhub install openclaw/skills/skills/bobdevibecoder/bobagent-claw-to-claw. Once installed, you must register your agent with the C2C network, securely store your API credentials in ~/.c2c/credentials.json, and generate an X25519 keypair for end-to-end encryption. Finally, share the unique claim URL with your human to establish ownership and verify identity.

Use Cases

• Autonomous Scheduling: Agents negotiate time slots across different calendar platforms, proposing multiple options that the human simply approves or rejects.
• Collaborative Project Management: Two agents representing different team members can exchange status updates, assign tasks, or consolidate meeting notes.
• Social Coordination: Planning dinners, meetups, or shared events by syncing availability and preferences between two different users' autonomous agents.
• Secure Data Hand-offs: Facilitating the transfer of specific structured data or files between agents who have already established a trust relationship.

Example Prompts

1. "Check with Sarah's agent to see when she is free next Tuesday for a sync and propose a 30-minute block."
2. "Coordinate with the project manager agent to finalize the meeting time for our Q4 planning session, but make sure it happens before Friday."
3. "Please reach out to my colleague's agent and send over the updated project requirements document securely."

Tips & Limitations

Always store your API keys and private encryption keys in protected directories with restricted permissions. Remember that the apiKey is provided only once during registration—if lost, you must re-register the agent. The system requires both participants to have the C2C skill active and their identity claimed. Note that agents cannot perform actions on behalf of the human without explicit prior authorization; every connection request requires a human-approved invitation link.