pilot-consensus
/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)
- Author
- TeoSlayer ↗
- Repository
- pilot-skills ↗
- Licence
- AGPL-3.0
- Last repository change
- 24.09.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 24.09.2026, without references to retired models or APIs.
AGPL-3.0, copyleft: przeróbki udostępniane innym muszą mieć tę samą licencję.
What it does and when to use it
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)
Original author description
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)
How it works
- Commands
- Workflow Example
- Dependencies
SKILL.md preview
---
name: pilot-consensus
description: >
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)
tags:
- pilot-protocol
- consensus
- voting
- coordination
license: AGPL-3.0
compatibility: >
Requires pilot-protocol skill and pilotctl binary on PATH.
The daemon must be running (pilotctl daemon start).
metadata:
author: vulture-labs
version: "1.0"
openclaw:
requires:
bins:
- pilotctl
homepage: https://pilotprotocol.network
allowed-tools:
- Bash
---
# pilot-consensus
Implement distributed consensus protocols for multi-agent coordination.
## Commands
### Propose a value
```bash
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
```bash
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
```bash
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:
```bash
#!/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.
Files in this package (2)
- README.md 1 KB
- SKILL.md 3 KB
Versions
The database has no other skills named pilot-consensus.
Database snapshot: 13.11.2026 · package version 34e05a366b48 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95pilot-leader-election
Elect a coordinator with automatic failover using heartbeat-based leader election. Use this skill when: 1. A swarm needs a single coordinator for decision making 2. You need automatic failover when the current leader fails 3. You want to avoid split-brain with deterministic… - 100hive-mind
Byzantine fault-tolerant consensus and distributed coordination. Queen-led hierarchical swarm management with multiple consensus strategies. Use when: distributed coordination, fault-tolerant operations, multi-agent consensus, collective decision making. Skip when: single-agent… - 95pilot-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… - 90swarm-consensus
Implement voting mechanisms (majority, weighted) to resolve inter-agent conflicts. Use when: swarm consensus. - 90acr-consensus-gate
Use when deliberating, proposing, or voting on actions requiring 67% Byzantine consensus quorum, casting ballots, or evaluating dissent rationales. - 100deploy-multi-agent-swarm
Deploy Multi-Agent Swarm — configure decentralized agent topology, bidding protocol, consensus voting, parallel execution, conflict resolution, swarm state store. Use when: deploy, provision swarm.