agent-raft-manager
- Repo stars 54,444
- Author updated Live
- Author repo ruflo
- Domain
- AI
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @ruvnet · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- macOS · Linux · Windows
- Runtime requirements
- Node.js
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: agent-raft-manager
description: Agent skill for raft-manager - invoke with $agent-raft-manager name: raft-manager type: coordina…
category: ai
runtime: Node.js
---
# agent-raft-manager output preview
## PART A: Task fit
- Use case: Agent skill for raft-manager - invoke with $agent-raft-manager name: raft-manager type: coordinator color: "#2196F3" description: Manages Raft consensus algorithm with leader election and log replication echo "🗳️ Raft Manager starting: $TASK" runs entirely locally; runs on Node.js. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Core Responsibilities / Implementation Approach / Leader Election Protocol” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Agent skill for raft-manager - invoke with $agent-raft-manager name: raft-manager type: coordinator color: "#2196F3" description: Manages Raft consensus algorithm with leader election and log replication echo "🗳️ Raft Manager starting: $TASK" runs entirely locally; runs on Node.js. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Core Responsibilities / Implementation Approach / Leader Election Protocol” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Validate with a small run
Start with a small task and check whether the result follows “Core Responsibilities / Implementation Approach / Leader Election Protocol”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: agent-raft-manager
description: Agent skill for raft-manager - invoke with $agent-raft-manager name: raft-manager type: coordina…
category: ai
source: ruvnet/ruflo
---
# agent-raft-manager
## When to use
- Agent skill for raft-manager - invoke with $agent-raft-manager name: raft-manager type: coordinator color: "#2196F3" d…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Core Responsibilities / Implementation Approach / Leader Election Protocol” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "agent-raft-manager" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Core Responsibilities / Implementation Approach / Leader Election Protocol
rules -> SKILL.md triggers / order / output contract
runtime -> Node.js | read files, write/modify files, run shell commands | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}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
- Leader Election: Coordinate randomized timeout-based leader selection
- Log Replication: Ensure reliable propagation of entries to followers
- Consistency Management: Maintain log consistency across all cluster nodes
- Membership Changes: Handle dynamic node addition$removal safely
- 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
Decide Fit First
Design Intent
How To Use It
Boundaries And Review