How do I install the Pilot Gossip skill?

Run npx skillmds@latest add teoslayer/pilot-gossip 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 Gossip 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 Gossip?

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 Gossip free to use?

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

Who published Pilot Gossip?

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

Pilot Gossip by teoslayer — Agent Skill

Name: Pilot Gossip
Author: TeoSlayer

Pilot Gossip

Gossip protocol for eventually-consistent shared state propagation across swarms. Use this skill when: 1. You need eventually-consistent state replication without coordination 2. Agents should share updates with random subsets of peers 3. You want epidemic-style information dissemination Do NOT use this skill when: - You need strong consistency (use pilot-consensus) - You need ordered message delivery (use leader-based broadcast)

TeoSlayer ed9e071 2 files · 2.9 KB Updated Sep 17, 2026

File contents

pilot-gossip

Implement gossip protocols for eventually-consistent state propagation in agent swarms.

This skill enables agents to share state updates by randomly selecting peers and exchanging information, achieving eventual consistency without centralized coordination.

Commands

Publish state update to random peers

FANOUT=3
PEERS=$(pilotctl --json peers --search "swarm:$SWARM_NAME" | jq -r '.[].address' | shuf -n $FANOUT)

for peer in $PEERS; do
  pilotctl --json send-message "$peer" \
    --data "{\"type\":\"gossip_push\",\"version\":$STATE_VERSION,\"state\":$STATE_DATA,\"sender\":\"$AGENT_ID\",\"timestamp\":\"$(date -u +%s)\"}" &
done
wait

Merge received state updates

GOSSIP_MSGS=$(pilotctl --json received | jq '[.messages[] | select(.payload.type == "gossip_push")]')

for msg in $(echo "$GOSSIP_MSGS" | jq -r '.[] | @base64'); do
  PAYLOAD=$(echo "$msg" | base64 -d)
  REMOTE_VERSION=$(echo "$PAYLOAD" | jq -r '.payload.version')

  if [ "$REMOTE_VERSION" -gt "$MY_VERSION" ]; then
    MY_STATE=$(echo "$MY_STATE $REMOTE_STATE" | jq -s '.[0] * .[1]')
    MY_VERSION=$REMOTE_VERSION
  fi
done

Workflow Example

Distributed key-value store with gossip replication:

#!/bin/bash
SWARM_NAME="kv-store-cluster"
AGENT_ID=$(pilotctl --json info | jq -r '.node_id')

# Gossip loop
for round in $(seq 1 10); do
  # Push to random peers
  PEERS=$(pilotctl --json peers --search "swarm:$SWARM_NAME" | jq -r '.[].address' | shuf -n 3)

  for peer in $PEERS; do
    pilotctl --json send-message "$peer" \
      --data "{\"type\":\"gossip_push\",\"version\":$MY_VERSION,\"state\":$MY_STATE,\"sender\":\"$AGENT_ID\"}" &
  done
  wait

  sleep 5
done

Dependencies

Requires pilot-protocol skill, jq, shuf, and base64.

---name: pilot-gossipdescription: Gossip protocol for eventually-consistent shared state propagation across swarms. Use this skill when: 1. You need eventually-consistent state replication without coordination 2. Agents should share updates with random subsets of peers 3. You want epidemic-style information dissemination Do NOT use this skill when: - You need strong consistency (use pilot-consensus) - You need ordered message delivery (use leader-based broadcast)license: AGPL-3.0---# pilot-gossipImplement gossip protocols for eventually-consistent state propagation in agent swarms.This skill enables agents to share state updates by randomly selecting peers and exchanging information, achieving eventual consistency without centralized coordination.## Commands### Publish state update to random peers```bashFANOUT=3PEERS=$(pilotctl --json peers --search "swarm:$SWARM_NAME" | jq -r '.[].address' | shuf -n $FANOUT)for peer in $PEERS; do pilotctl --json send-message "$peer" \ --data "{\"type\":\"gossip_push\",\"version\":$STATE_VERSION,\"state\":$STATE_DATA,\"sender\":\"$AGENT_ID\",\"timestamp\":\"$(date -u +%s)\"}" &donewait```### Merge received state updates```bashGOSSIP_MSGS=$(pilotctl --json received | jq '[.messages[] | select(.payload.type == "gossip_push")]')for msg in $(echo "$GOSSIP_MSGS" | jq -r '.[] | @base64'); do PAYLOAD=$(echo "$msg" | base64 -d) REMOTE_VERSION=$(echo "$PAYLOAD" | jq -r '.payload.version') if [ "$REMOTE_VERSION" -gt "$MY_VERSION" ]; then MY_STATE=$(echo "$MY_STATE $REMOTE_STATE" | jq -s '.[0] * .[1]') MY_VERSION=$REMOTE_VERSION fidone```## Workflow ExampleDistributed key-value store with gossip replication:```bash#!/bin/bashSWARM_NAME="kv-store-cluster"AGENT_ID=$(pilotctl --json info | jq -r '.node_id')# Gossip loopfor round in $(seq 1 10); do # Push to random peers PEERS=$(pilotctl --json peers --search "swarm:$SWARM_NAME" | jq -r '.[].address' | shuf -n 3) for peer in $PEERS; do pilotctl --json send-message "$peer" \ --data "{\"type\":\"gossip_push\",\"version\":$MY_VERSION,\"state\":$MY_STATE,\"sender\":\"$AGENT_ID\"}" & done wait sleep 5done```## DependenciesRequires pilot-protocol skill, jq, shuf, and base64.

Frequently asked questions