How do I install the Pilot Formation skill?

Run npx skillmds@latest add teoslayer/pilot-formation in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pilot Formation safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pilot Formation?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pilot Formation free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under AGPL-3.

Who published Pilot Formation?

TeoSlayer (@teoslayer) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pilot Formation by teoslayer — Agent Skill

Name: Pilot Formation
Author: TeoSlayer

Pilot Formation

Deploy predefined network topologies (star, ring, mesh, tree) for structured swarms. Use this skill when: 1. You need specific communication patterns (star coordinator, ring consensus) 2. You want to minimize connection overhead with structured topologies 3. You need hierarchical organization (tree) for scaling Do NOT use this skill when: - Ad-hoc peer discovery is sufficient (use pilot-swarm-join) - Topology changes frequently (use dynamic mesh)

TeoSlayer c1cf640 2 files · 3.5 KB Updated Sep 17, 2026

File contents

pilot-formation

Deploy structured network topologies with automatic peer handshaking and trust establishment. Supports star (hub-and-spoke), ring (circular), mesh (all-to-all), tree (hierarchical), and line (chain) formations.

Commands

Deploy star (hub connects to all spokes):

WORKERS=$(pilotctl --json peers --search "role:worker" | jq -r '.[].hostname')
for worker in $WORKERS; do
  pilotctl --json handshake "$worker" "Forming star topology"
  sleep 1
  NODE_ID=$(pilotctl --json pending | jq -r '.pending[] | select(.hostname == "'"$worker"'") | .node_id')
  [ -n "$NODE_ID" ] && pilotctl --json approve "$NODE_ID"
done

Deploy ring (circular connections):

AGENTS=$(pilotctl --json peers --search "swarm:$SWARM_NAME" | jq -r 'sort_by(.node_id) | .[].address')
# Connect to next agent in sorted order (implementation in workflow)

Deploy mesh (all-to-all):

ALL_PEERS=$(pilotctl --json peers --search "swarm:$SWARM_NAME" | jq -r '.[].address')
for peer in $ALL_PEERS; do
  pilotctl --json handshake "$peer" "Forming mesh topology" &
done
wait

# Approve all pending handshakes
PENDING=$(pilotctl --json pending | jq -r '.[].node_id')
for peer in $PENDING; do
  pilotctl --json approve "$peer" &
done
wait

Workflow Example

#!/bin/bash
# Deploy star topology

SWARM_NAME="task-swarm"
MY_ADDR=$(pilotctl --json info | jq -r '.address')
REGISTRY_HOST="registry.example.com"

# Get swarm members
SWARM_MEMBERS=$(pilotctl --json peers --search "swarm:$SWARM_NAME" | jq -r '.[].address')

echo "Deploying star topology (hub: $MY_ADDR)"

# Hub connects to all spokes
for worker in $SWARM_MEMBERS; do
  if [ "$worker" != "$MY_ADDR" ]; then
    echo "Connecting to spoke: $worker"
    pilotctl --json handshake "$worker" "Forming star topology"
    sleep 1
    NODE_ID=$(pilotctl --json pending | jq -r '.pending[] | select(.hostname == "'"$worker"'") | .node_id')
    [ -n "$NODE_ID" ] && pilotctl --json approve "$NODE_ID"
  fi
done

# Publish topology
pilotctl --json publish "$REGISTRY_HOST" "topology:$SWARM_NAME" \
  --data "{\"type\":\"star\",\"hub\":\"$MY_ADDR\",\"formed_at\":\"$(date -u +%Y-%m-%dT%H:%M:%SZ)\"}"

echo "Star topology complete"

Dependencies

Requires pilot-protocol skill, pilotctl binary, running daemon, and jq for JSON parsing.

---name: pilot-formationdescription: Deploy predefined network topologies (star, ring, mesh, tree) for structured swarms. Use this skill when: 1. You need specific communication patterns (star coordinator, ring consensus) 2. You want to minimize connection overhead with structured topologies 3. You need hierarchical organization (tree) for scaling Do NOT use this skill when: - Ad-hoc peer discovery is sufficient (use pilot-swarm-join) - Topology changes frequently (use dynamic mesh)license: AGPL-3.0---# pilot-formationDeploy structured network topologies with automatic peer handshaking and trust establishment. Supports star (hub-and-spoke), ring (circular), mesh (all-to-all), tree (hierarchical), and line (chain) formations.## Commands**Deploy star (hub connects to all spokes):**```bashWORKERS=$(pilotctl --json peers --search "role:worker" | jq -r '.[].hostname')for worker in $WORKERS; do pilotctl --json handshake "$worker" "Forming star topology" sleep 1 NODE_ID=$(pilotctl --json pending | jq -r '.pending[] | select(.hostname == "'"$worker"'") | .node_id') [ -n "$NODE_ID" ] && pilotctl --json approve "$NODE_ID"done```**Deploy ring (circular connections):**```bashAGENTS=$(pilotctl --json peers --search "swarm:$SWARM_NAME" | jq -r 'sort_by(.node_id) | .[].address')# Connect to next agent in sorted order (implementation in workflow)```**Deploy mesh (all-to-all):**```bashALL_PEERS=$(pilotctl --json peers --search "swarm:$SWARM_NAME" | jq -r '.[].address')for peer in $ALL_PEERS; do pilotctl --json handshake "$peer" "Forming mesh topology" &donewait# Approve all pending handshakesPENDING=$(pilotctl --json pending | jq -r '.[].node_id')for peer in $PENDING; do pilotctl --json approve "$peer" &donewait```## Workflow Example```bash#!/bin/bash# Deploy star topologySWARM_NAME="task-swarm"MY_ADDR=$(pilotctl --json info | jq -r '.address')REGISTRY_HOST="registry.example.com"# Get swarm membersSWARM_MEMBERS=$(pilotctl --json peers --search "swarm:$SWARM_NAME" | jq -r '.[].address')echo "Deploying star topology (hub: $MY_ADDR)"# Hub connects to all spokesfor worker in $SWARM_MEMBERS; do if [ "$worker" != "$MY_ADDR" ]; then echo "Connecting to spoke: $worker" pilotctl --json handshake "$worker" "Forming star topology" sleep 1 NODE_ID=$(pilotctl --json pending | jq -r '.pending[] | select(.hostname == "'"$worker"'") | .node_id') [ -n "$NODE_ID" ] && pilotctl --json approve "$NODE_ID" fidone# Publish topologypilotctl --json publish "$REGISTRY_HOST" "topology:$SWARM_NAME" \ --data "{\"type\":\"star\",\"hub\":\"$MY_ADDR\",\"formed_at\":\"$(date -u +%Y-%m-%dT%H:%M:%SZ)\"}"echo "Star topology complete"```## DependenciesRequires `pilot-protocol` skill, `pilotctl` binary, running daemon, and `jq` for JSON parsing.

Frequently asked questions