Pilot a2a bridge

Skill TeoSlayer/pilot-skills/skills/pilot-a2a-bridge

80+ agent skills for Pilot Protocol — communication, file transfer, trust, task routing, swarm coordination, and more

Install

npx -y skills add TeoSlayer/pilot-skills --skill pilot-a2a-bridge

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Bridge A2A (Agent-to-Agent) protocol messages over Pilot tunnels. Use this skill when: 1. You need to connect A2A agents across different networks 2. You want to route A2A messages through Pilot's overlay network 3. You're building multi-agent systems that need reliable messaging Do NOT use this skill when: - Agents are on the same local network (use direct A2A instead) - You need raw TCP/UDP access (use pilot-protocol directly) - The daemon is not running

The file declares its own license as AGPL-3.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.2 KB, as published. Nobody here has run it

Pilot A2A Bridge

Bridge Agent-to-Agent protocol messages over Pilot tunnels with NAT traversal and encryption.

Commands

Start A2A Bridge

pilotctl --json daemon start --hostname a2a-agent-1
pilotctl --json listen 5000

Send A2A Message

pilotctl --json send-message remote-agent --data '{"type":"task","action":"analyze","payload":"data"}'

Subscribe to A2A Events

pilotctl --json subscribe remote-agent a2a-events

Receive A2A Messages

pilotctl --json recv 5000

Workflow Example

#!/bin/bash
# Agent A: A2A bridge listener

pilotctl --json daemon start --hostname agent-a
pilotctl --json listen 5000

while true; do
  MSG=$(pilotctl --json recv 5000 --timeout 30s)
  TYPE=$(echo "$MSG" | jq -r '.type')
  SENDER=$(echo "$MSG" | jq -r '.sender')

  case "$TYPE" in
    task)
      RESULT=$(process_task "$(echo "$MSG" | jq -r '.payload')")
      pilotctl --json send-message "$SENDER" --data "{\"type\":\"result\",\"data\":\"$RESULT\"}"
      ;;
  esac
done

Message Format

{
  "type": "task|result|event|status",
  "action": "analyze|process|compute",
  "payload": "arbitrary data"
}

Dependencies

Requires pilot-protocol skill with running daemon and A2A-compatible agents.