pilot-leader-election

Elect a single leader among swarm agents with heartbeat-based failover and deterministic tie-breaking.

7|3|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-leader-election
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pilot-leader-election
Source: https://github.com/TeoSlayer/pilot-skills/tree/main/skills/pilot-leader-election
Command: npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-leader-election

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating a swarm requires a single, reliable coordinator and a safe failover path when leaders die or become partitioned.

Core Features & Use Cases

  • Automatic leader election among swarm agents
  • Heartbeat-based failover with deterministic tie-breaking
  • Seamless integration with Pilot Protocol and pilotctl

Quick Start

Start the daemon, install this skill, and trigger the initial leader election.

Frequently Asked Questions about pilot-leader-election

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does automatic leader election work for swarm coordination?

Automatic leader election works by coordinating swarm agents to elect a single stable coordinator for task routing, using heartbeat-based failover with deterministic tie-breaking to maintain leadership continuity during node failures or network partitions.

How do I set up leader election with pilotctl for swarm failover?

To set up leader election, start the Pilot daemon, install this skill, and trigger the initial election using the pilotctl binary on PATH to ensure your swarm agents coordinate under a single elected leader.

Do I need the pilot-protocol skill to run automatic leader election?

Yes, you need the pilot-protocol skill, the pilotctl binary on PATH, and a running Pilot daemon to enable automatic leader election and heartbeat-based failover for your swarm.

What happens to swarm coordination when the leader node dies?

When the leader node dies or becomes partitioned, heartbeat-based failover triggers an automatic leader election with deterministic tie-breaking to seamlessly assign a new stable coordinator for task routing.

When should I use automatic leader election instead of manual swarm coordination?

You should use automatic leader election when your swarm requires a stable coordinator for task routing and needs guaranteed leadership continuity during node failures, avoiding manual recovery interventions.