Pilot Swarm Config
Distributed configuration management for agent swarms with versioned updates. Use this skill when: 1. Multiple agents need to share configuration settings 2. You need to push config updates to all swarm members 3. You want versioned config with rollback capability Do NOT use this skill when: - Configuration is static and set at startup (use local config files) - Each agent has unique config (no sharing needed)
Install
npx skills add TeoSlayer/pilot-skills --skill pilot-swarm-configgit clone --depth 1 https://github.com/TeoSlayer/pilot-skills.git /tmp/pilot-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pilot-skills/skills/pilot-swarm-config ~/.claude/skills/pilot-swarm-configPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# pilot-swarm-config
Manage shared configuration across agent swarms with versioning, atomic updates, and rollback support.
## Essential Commands
### Publish configuration update
```bash
CONFIG_VERSION=$(date +%s)
CONFIG_DATA='{"max_workers":10,"timeout_ms":5000,"log_level":"info"}'
pilotctl --json publish "registry-hostname" "config:$SWARM_NAME" \
--data "{\"type\":\"config_update\",\"version\":$CONFIG_VERSION,\"config\":$CONFIG_DATA}"
```
### Subscribe to configuration updates
```bash
pilotctl --json subscribe "registry-hostname" "config:$SWARM_NAME"
```
### Apply configuration locally
```bash
LATEST_CONFIG=$(pilotctl --json inbox \
| jq '[.messages[] | select(.topic == "config:'$SWARM_NAME'" and .payload.type == "config_update")] | sort_by(.payload.version) | last')
CONFIG_VERSION=$(echo "$LATEST_CONFIG" | jq -r '.payload.version')
CONFIG_DATA=$(echo "$LATEST_CONFIG" | jq -r '.payload.config')
echo "$CONFIG_DATA" > /tmp/swarm-config.json
echo "$CONFIG_VERSION" > /tmp/swarm-config-version.txt
```
### Validate configuration
```bash
# Basic validation
VALID=$(echo "$CONFIG_DATA" | jq 'has("max_workers") and has("timeout_ms")')
if [ "$VALID" = "true" ]; then
echo "Config validation passed"
else
echo "Config validation FAILED"
exit 1
fi
```
### Rollback to previous versionDetails
- Skill name
pilot-swarm-config- Repository
- TeoSlayer/pilot-skills
- Path
skills/pilot-swarm-config/SKILL.md- License
- AGPL-3.0
- Repo updated
- 9 November 2026
FAQ
What does the Pilot Swarm Config skill do?
Distributed configuration management for agent swarms with versioned updates. Use this skill when: 1. Multiple agents need to share configuration settings 2. You need to push config updates to all swarm members 3. You want versioned config with rollback capability Do NOT use this skill when: - Configuration is static and set at startup (use local config files) - Each agent has unique config (no sharing needed)
How do I install the Pilot Swarm Config skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add TeoSlayer/pilot-skills --skill pilot-swarm-config. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Pilot Swarm Config popular?
It lives in TeoSlayer/pilot-skills, which has 9 GitHub stars and 3 forks.
Related skills
Pilot A2a Bridge
9TeoSlayer/pilot-skills
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
Pilot Ad Campaign Manager Setup
9TeoSlayer/pilot-skills
Deploy an ad campaign management system with 4 agents that automate campaign strategy, creative production, real-time bidding, and performance analytics. Use this skill when: 1. User wants to set up an automated ad campaign management pipeline 2. User is configuring an agent as part of an advertising or media buying workflow 3. User asks about automating campaign strategy, creative testing, or bid optimization across agents Do NOT use this skill when: - User wants to track a single metric (use pilot-metrics instead) - User wants a one-off data stream (use pilot-stream-data instead)
Pilot Agent Marketplace Setup
9TeoSlayer/pilot-skills
Deploy a decentralized agent marketplace with 4 agents. Use this skill when: 1. User wants to set up an agent capability marketplace 2. User is configuring a directory, matchmaker, escrow, or gateway agent 3. User asks about capability discovery, auctions, or escrow settlement Do NOT use this skill when: - User wants to discover a single agent (use pilot-discover instead) - User wants to run a single auction (use pilot-auction instead)
Pilot Swarm Join
9TeoSlayer/pilot-skills
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)
Pilot Stream Data
9TeoSlayer/pilot-skills
Real-time NDJSON data streaming over persistent Pilot Protocol connections. Use this skill when: 1. You need to stream structured data in real-time between agents 2. You want to send continuous sensor readings, logs, or metrics 3. You need bidirectional streaming communication with backpressure Do NOT use this skill when: - You need to transfer files (use pilot-share or pilot-sync) - You need pub/sub broadcast (use pilot-pubsub instead) - You need request/response patterns (use pilot-rpc instead)
Pilot Sync
9TeoSlayer/pilot-skills
Bidirectional file synchronization between agents over the Pilot Protocol network. Use this skill when: 1. You need to keep directories synchronized between two agents 2. You want to replicate files across multiple nodes with conflict detection 3. You need to maintain consistent file state across distributed agents Do NOT use this skill when: - You only need one-way file transfer (use pilot-share instead) - You need real-time streaming data (use pilot-stream-data instead) - Files are larger than 100MB without chunking support (use pilot-chunk-transfer)
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.