Pilot swarm join

Skill TeoSlayer/pilot-skills/skills/pilot-swarm-join

Join or create agent swarms with auto-discovery and peer mesh formation. Use this skill when: 1. An agent needs to join an existing swarm or create a new one 2. You need to discover and connect to peers in a named swarm 3. You want to establish bidirectional trust with swarm members Do NOT use this skill when: - You only need point-to-point communication (use pilot-p2p-connect) - You need structured topologies like star or tree (use pilot-formation)From its SKILL.md

Install

npx -y skills add TeoSlayer/pilot-skills --skill pilot-swarm-join

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 file declares

Copied from the file, not written here

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.7 KB, 534 tokens by cl100k_base, as published. Nobody here has run it

pilot-swarm-join

Join or create named agent swarms with automatic peer discovery and mesh trust establishment.

Commands

Join Swarm

pilotctl --json publish "registry-hostname" "swarm:$SWARM_NAME" --data "{\"agent\":\"$AGENT_ID\",\"role\":\"worker\"}"

Subscribe to Swarm

pilotctl --json subscribe "registry-hostname" "swarm:$SWARM_NAME"

Discover Peers

PEERS=$(pilotctl --json inbox | jq -r '.messages[] | select(.topic == "swarm:'$SWARM_NAME'") | .sender')

Handshake with Peers

for peer in $PEERS; do
  pilotctl --json handshake "$peer" "Joining swarm $SWARM_NAME"
done

Approve Peers

pilotctl --json pending | jq -r '.[].node_id' | xargs -I {} pilotctl --json approve {}

Leave Swarm

pilotctl --json publish "registry-hostname" "swarm:$SWARM_NAME" --data "{\"agent\":\"$AGENT_ID\",\"action\":\"leave\"}"

Workflow Example

#!/bin/bash
# Join compute swarm

SWARM_NAME="compute-cluster-01"
AGENT_ID=$(pilotctl --json info | jq -r '.node_id')
REGISTRY_HOST="registry.example.com"

# Announce presence
pilotctl --json publish "$REGISTRY_HOST" "swarm:$SWARM_NAME" \
  --data "{\"agent\":\"$AGENT_ID\",\"role\":\"worker\",\"joined_at\":\"$(date -u +%Y-%m-%dT%H:%M:%SZ)\"}"

# Subscribe to swarm updates
pilotctl --json subscribe "$REGISTRY_HOST" "swarm:$SWARM_NAME"
sleep 2

# Discover peers
PEERS=$(pilotctl --json inbox | jq -r '.messages[] | select(.topic == "swarm:'$SWARM_NAME'") | .payload.agent')

# Handshake with peers
for peer in $PEERS; do
  pilotctl --json handshake "$peer" "Joining swarm $SWARM_NAME"
done

# Approve handshakes
pilotctl --json pending | jq -r '.[].node_id' | xargs -I {} pilotctl --json approve {}

Dependencies

Requires pilot-protocol, pilotctl, jq, and running daemon with registry connection.

What ships with it: 1 file

708 B alongside SKILL.md

README.md708 B