Agent Raft Manager
Coordinate Raft leader election, log replication, and membership changes in distributed agent or backend clusters.
Overview
agent-raft-manager is an agent skill for the Operate phase that structures Raft leader election, log replication, and membership operations for distributed clusters.
Install
npx skills add https://github.com/ruvnet/ruflo --skill agent-raft-managerWhat is this skill?
- Coordinator skill typed as raft-manager with leader_election, log_replication, follower_management, membership_changes,
- Documents 5 core responsibilities from election through recovery after network partitions
- Pre/post hooks echo cluster health checks before elections and log consistency validation after operations
- Priority marked high within the ruflo agent stack for consensus-critical tasks
- 5 documented core responsibilities for Raft management
- 5 capability tags in frontmatter (election through consistency_verification)
Adoption & trust: 641 installs on skills.sh; 58.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your clustered service needs strong consistency but agent-assisted changes risk botched elections, divergent logs, or unsafe membership updates.
Who is it for?
Indie teams operating self-managed Raft clusters who want agent workflows aligned to election and replication rituals.
Skip if: Single-node prototypes or teams on fully managed databases where Raft is an implementation detail you never touch.
When should I use this skill?
Invoke with $agent-raft-manager when tasks involve Raft elections, replication, followers, membership, or consistency checks.
What do I get? / Deliverables
Raft operations run through a documented coordinator flow with pre-election health checks and post-operation consistency validation steps.
- Election and replication runbook steps executed via agent
- Post-operation consistency validation checklist
Recommended Skills
Journey fit
Canonical shelf is Operate because Raft management is about keeping production-like distributed nodes consistent, not greenfield UI work. Infra is correct for consensus, quorum health checks, and recovery after partitions in clustered deployments.
How it compares
Operational procedure skill for Raft coordination, not a hosted consensus SaaS or generic bash deploy script.
Common Questions / FAQ
Who is agent-raft-manager for?
Builders using Ruflo-style agents who operate multi-node systems and need structured guidance for Raft elections, replication, and recovery.
When should I use agent-raft-manager?
Use it in Operate infra when planning leader transitions, verifying follower catch-up, or handling membership changes after deploys or incidents.
Is agent-raft-manager safe to install?
It may trigger shell hooks around cluster tasks; review the Security Audits panel on this Prism page and restrict agent shell access on production quorum nodes.
SKILL.md
READMESKILL.md - Agent Raft Manager
--- name: raft-manager type: coordinator color: "#2196F3" description: Manages Raft consensus algorithm with leader election and log replication capabilities: - leader_election - log_replication - follower_management - membership_changes - consistency_verification priority: high hooks: pre: | echo "🗳️ Raft Manager starting: $TASK" # Check cluster health before operations if [[ "$TASK" == *"election"* ]]; then echo "🎯 Preparing leader election process" fi post: | echo "📝 Raft operation complete" # Verify log consistency echo "🔍 Validating log replication and consistency" --- # Raft Consensus Manager Implements and manages the Raft consensus algorithm for distributed systems with strong consistency guarantees. ## Core Responsibilities 1. **Leader Election**: Coordinate randomized timeout-based leader selection 2. **Log Replication**: Ensure reliable propagation of entries to followers 3. **Consistency Management**: Maintain log consistency across all cluster nodes 4. **Membership Changes**: Handle dynamic node addition$removal safely 5. **Recovery Coordination**: Resynchronize nodes after network partitions ## Implementation Approach ### Leader Election Protocol - Execute randomized timeout-based elections to prevent split votes - Manage candidate state transitions and vote collection - Maintain leadership through periodic heartbeat messages - Handle split vote scenarios with intelligent backoff ### Log Replication System - Implement append entries protocol for reliable log propagation - Ensure log consistency guarantees across all follower nodes - Track commit index and apply entries to state machine - Execute log compaction through snapshotting mechanisms ### Fault Tolerance Features - Detect leader failures and trigger new elections - Handle network partitions while maintaining consistency - Recover failed nodes to consistent state automatically - Support dynamic cluster membership changes safely ## Collaboration - Coordinate with Quorum Manager for membership adjustments - Interface with Performance Benchmarker for optimization analysis - Integrate with CRDT Synchronizer for eventual consistency scenarios - Synchronize with Security Manager for secure communication