How do I install the Pilot Consensus skill?

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

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

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

Who published Pilot Consensus?

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

Pilot Consensus by teoslayer — Agent Skill

Name: Pilot Consensus
Author: TeoSlayer

Pilot Consensus

Distributed voting and agreement protocols for multi-agent decision making. Use this skill when: 1. Multiple agents need to agree on a value or decision 2. You need Byzantine fault-tolerant consensus in a swarm 3. You want to coordinate distributed transactions or state changes Do NOT use this skill when: - A single leader can make decisions (use pilot-leader-election) - You only need eventual consistency (use pilot-gossip)

TeoSlayer b215f6b 2 files · 3.0 KB Updated Sep 17, 2026

File contents

pilot-consensus

Implement distributed consensus protocols for multi-agent coordination.

Commands

Propose a value

PROPOSAL_ID=$(uuidgen)
pilotctl --json publish "registry-hostname" "consensus:$CONSENSUS_GROUP" \
  --data "{\"type\":\"proposal\",\"id\":\"$PROPOSAL_ID\",\"proposer\":\"$AGENT_ID\",\"value\":$PROPOSAL_VALUE,\"term\":$CURRENT_TERM}"

Vote on a proposal

pilotctl --json send-message "$PROPOSER_ADDRESS" \
  --data "{\"type\":\"vote\",\"proposal_id\":\"$PROPOSAL_ID\",\"voter\":\"$AGENT_ID\",\"approve\":true,\"term\":$CURRENT_TERM}"

Collect votes and check quorum

VOTES=$(pilotctl --json received | jq '[.messages[] | select(.payload.type == "vote" and .payload.proposal_id == "'$PROPOSAL_ID'")]')
APPROVALS=$(echo "$VOTES" | jq '[.[] | select(.payload.approve == true)] | length')
QUORUM=$(( ($TOTAL_VOTERS / 2) + 1 ))

if [ "$APPROVALS" -ge "$QUORUM" ]; then
  echo "Consensus reached"
fi

Workflow Example

Three-phase consensus protocol:

#!/bin/bash
CONSENSUS_GROUP="config-update"
PROPOSAL_VALUE='{"max_workers":10}'
REGISTRY_HOST="registry.example.com"

# Phase 1: Prepare
PROPOSAL_ID=$(uuidgen)
pilotctl --json publish "$REGISTRY_HOST" "consensus:$CONSENSUS_GROUP" \
  --data "{\"type\":\"prepare\",\"id\":\"$PROPOSAL_ID\",\"value\":$PROPOSAL_VALUE,\"term\":$CURRENT_TERM}"

# Phase 2: Vote
sleep 3
VOTES=$(pilotctl --json received | jq '[.messages[] | select(.payload.type == "vote")]')
APPROVALS=$(echo "$VOTES" | jq '[.[] | select(.payload.approve == true)] | length')

# Phase 3: Commit
if [ "$APPROVALS" -ge "$QUORUM" ]; then
  pilotctl --json publish "$REGISTRY_HOST" "consensus:$CONSENSUS_GROUP" \
    --data "{\"type\":\"commit\",\"proposal_id\":\"$PROPOSAL_ID\",\"value\":$PROPOSAL_VALUE}"
fi

Dependencies

Requires pilot-protocol skill, jq, and uuidgen.

---name: pilot-consensusdescription: Distributed voting and agreement protocols for multi-agent decision making. Use this skill when: 1. Multiple agents need to agree on a value or decision 2. You need Byzantine fault-tolerant consensus in a swarm 3. You want to coordinate distributed transactions or state changes Do NOT use this skill when: - A single leader can make decisions (use pilot-leader-election) - You only need eventual consistency (use pilot-gossip)license: AGPL-3.0---# pilot-consensusImplement distributed consensus protocols for multi-agent coordination.## Commands### Propose a value```bashPROPOSAL_ID=$(uuidgen)pilotctl --json publish "registry-hostname" "consensus:$CONSENSUS_GROUP" \ --data "{\"type\":\"proposal\",\"id\":\"$PROPOSAL_ID\",\"proposer\":\"$AGENT_ID\",\"value\":$PROPOSAL_VALUE,\"term\":$CURRENT_TERM}"```### Vote on a proposal```bashpilotctl --json send-message "$PROPOSER_ADDRESS" \ --data "{\"type\":\"vote\",\"proposal_id\":\"$PROPOSAL_ID\",\"voter\":\"$AGENT_ID\",\"approve\":true,\"term\":$CURRENT_TERM}"```### Collect votes and check quorum```bashVOTES=$(pilotctl --json received | jq '[.messages[] | select(.payload.type == "vote" and .payload.proposal_id == "'$PROPOSAL_ID'")]')APPROVALS=$(echo "$VOTES" | jq '[.[] | select(.payload.approve == true)] | length')QUORUM=$(( ($TOTAL_VOTERS / 2) + 1 ))if [ "$APPROVALS" -ge "$QUORUM" ]; then echo "Consensus reached"fi```## Workflow ExampleThree-phase consensus protocol:```bash#!/bin/bashCONSENSUS_GROUP="config-update"PROPOSAL_VALUE='{"max_workers":10}'REGISTRY_HOST="registry.example.com"# Phase 1: PreparePROPOSAL_ID=$(uuidgen)pilotctl --json publish "$REGISTRY_HOST" "consensus:$CONSENSUS_GROUP" \ --data "{\"type\":\"prepare\",\"id\":\"$PROPOSAL_ID\",\"value\":$PROPOSAL_VALUE,\"term\":$CURRENT_TERM}"# Phase 2: Votesleep 3VOTES=$(pilotctl --json received | jq '[.messages[] | select(.payload.type == "vote")]')APPROVALS=$(echo "$VOTES" | jq '[.[] | select(.payload.approve == true)] | length')# Phase 3: Commitif [ "$APPROVALS" -ge "$QUORUM" ]; then pilotctl --json publish "$REGISTRY_HOST" "consensus:$CONSENSUS_GROUP" \ --data "{\"type\":\"commit\",\"proposal_id\":\"$PROPOSAL_ID\",\"value\":$PROPOSAL_VALUE}"fi```## DependenciesRequires pilot-protocol skill, jq, and uuidgen.

Frequently asked questions