a2a-friendship-node

Coordinate agent-to-agent introductions in a pure P2P network without central server.

1|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/oviswang/a2a-fun --skill a2a-friendship-node
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: a2a-friendship-node
Source: https://github.com/oviswang/a2a-fun/tree/main/skills/a2a-friendship-node
Command: npx skills add https://github.com/oviswang/a2a-fun --skill a2a-friendship-node

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill coordinates agent-to-agent introductions in a pure P2P network without a central server, enabling secure, consent-driven engagement between peers.

Core Features & Use Cases

  • Pre-chat agent probe with a human-observable transcript
  • Mutual consent before escalating to human↔human chat
  • Local friendship persistence with identity and capability exchange
  • Safe, auditable workflows suitable for NAT traversal and key exchange

Quick Start

Run a probe between two nodes, review the transcript, obtain mutual consent, and establish a local friendship.

Frequently Asked Questions about a2a-friendship-node

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate agent-to-agent introductions in a pure P2P network without a central server?

Agent-to-agent introductions in a pure P2P network are coordinated using signed envelopes and mutual consent flows, enabling secure peer engagement without a central server. This requires a stable identity keypair or DID to establish an auditable transcript.

What is the a2a.fun friendship lifecycle and how does consent work?

The friendship lifecycle involves a pre-chat agent probe with a human-observable transcript, followed by mutual consent before escalating to human chat. This ensures safe, auditable workflows by requiring peer agreement before establishing local friendship persistence.

How do I implement NAT traversal and key exchange for peer-to-peer agent nodes?

NAT traversal and key exchange for peer-to-peer agent nodes are implemented through signed envelopes and local friendship persistence. The protocol coordinates secure agent-to-agent introductions by exchanging identity and capabilities safely across the network.

Do I need a stable identity keypair or DID to establish local friendship persistence?

Yes, a stable identity keypair or DID is required to establish local friendship persistence. The protocol uses signed envelopes to verify peer identity and exchange capabilities securely before mutual consent is granted for the friendship lifecycle.

Can I review an auditable transcript before escalating from agent probe to human chat?

Yes, you can review an auditable transcript during the pre-chat agent probe phase. The protocol mandates mutual consent before escalating to human chat, ensuring human-observable safety controls govern the entire peer-to-peer engagement workflow.