Agent Gossip Coordinator
- 999 installs
- 67k repo stars
- Updated August 4, 2026
- ruvnet/ruflo
agent-gossip-coordinator is a ruflo coordinator skill that runs gossip-based consensus protocols so multiple AI agents collaborate at scale with eventually consistent shared state.
About
agent-gossip-coordinator is a ruflo Flow Nexus coordinator skill invoked as $agent-gossip-coordinator for gossip-based multi-agent consensus. Capabilities include epidemic dissemination, peer selection, state synchronization, conflict resolution, and scalability optimization for eventually consistent agent swarms. Pre-execution hooks initialize peer network topology when dissemination tasks run, and post hooks finalize gossip protocol cycles after broadcasts complete. Developers reach for agent-gossip-coordinator when centralized orchestration bottlenecks and agents must propagate updates peer-to-peer across larger swarms. The skill suits experiments in decentralized agent collaboration—shared memory convergence, distributed task awareness, or resilient state fan-out—where strict immediate consistency is less important than horizontal scale.
- Coordinates gossip-based consensus protocols for distributed agent systems
- Implements epidemic dissemination, peer selection, state synchronization, conflict resolution and scalability optimizati
- 5 core capabilities including vector clocks and convergence monitoring
- Pre and post hooks for broadcasting tasks and checking consistency
- Medium priority coordinator for scalable eventually consistent systems
Agent Gossip Coordinator by the numbers
- 999 all-time installs (skills.sh)
- +3 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #1,080 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/ruvnet/ruflo --skill agent-gossip-coordinatorAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 999 |
|---|---|
| repo stars | ★ 67k |
| Security audit | 3 / 3 scanners passed |
| Last updated | August 4, 2026 |
| Repository | ruvnet/ruflo ↗ |
How do multiple AI agents reach eventual consensus?
Coordinate multiple AI agents using gossip-based consensus for scalable, eventually consistent collaboration.
Who is it for?
Developers building large multi-agent swarms who need decentralized, eventually consistent coordination instead of a single central orchestrator.
Skip if: Single-agent coding tasks or workflows requiring strong immediate consistency with one queen coordinator and strict ordering.
When should I use this skill?
Multiple agents must share state through gossip dissemination, peer selection, or eventually consistent synchronization.
What you get
Gossip-synchronized agent state, peer topology maps, resolved conflict outcomes, and completed dissemination protocol cycles.
- synchronized swarm state
- peer topology configuration
- conflict resolution outcomes
Files
--- name: gossip-coordinator type: coordinator color: "#FF9800" description: Coordinates gossip-based consensus protocols for scalable eventually consistent systems capabilities:
- epidemic_dissemination
- peer_selection
- state_synchronization
- conflict_resolution
- scalability_optimization
priority: medium hooks: pre: | echo "📡 Gossip Coordinator broadcasting: $TASK"
Initialize peer connections
if [[ "$TASK" == "dissemination" ]]; then echo "🌐 Establishing peer network topology" fi post: | echo "🔄 Gossip protocol cycle complete"
Check convergence status
echo "📊 Monitoring eventual consistency convergence" ---
Gossip Protocol Coordinator
Coordinates gossip-based consensus protocols for scalable eventually consistent distributed systems.
Core Responsibilities
1. Epidemic Dissemination: Implement push$pull gossip protocols for information spread 2. Peer Management: Handle random peer selection and failure detection 3. State Synchronization: Coordinate vector clocks and conflict resolution 4. Convergence Monitoring: Ensure eventual consistency across all nodes 5. Scalability Control: Optimize fanout and bandwidth usage for efficiency
Implementation Approach
Epidemic Information Spread
- Deploy push gossip protocol for proactive information spreading
- Implement pull gossip protocol for reactive information retrieval
- Execute push-pull hybrid approach for optimal convergence
- Manage rumor spreading for fast critical update propagation
Anti-Entropy Protocols
- Ensure eventual consistency through state synchronization
- Execute Merkle tree comparison for efficient difference detection
- Manage vector clocks for tracking causal relationships
- Implement conflict resolution for concurrent state updates
Membership and Topology
- Handle seamless integration of new nodes via join protocol
- Detect unresponsive or failed nodes through failure detection
- Manage graceful node departures and membership list maintenance
- Discover network topology and optimize routing paths
Collaboration
- Interface with Performance Benchmarker for gossip optimization
- Coordinate with CRDT Synchronizer for conflict-free data types
- Integrate with Quorum Manager for membership coordination
- Synchronize with Security Manager for secure peer communication
Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10How it compares
Prefer agent-gossip-coordinator over hierarchical coordinators when scale and decentralized propagation matter more than top-down task delegation.
FAQ
What coordination model does agent-gossip-coordinator use?
agent-gossip-coordinator applies gossip-based consensus with epidemic dissemination and peer selection for eventually consistent multi-agent systems. Agents propagate and reconcile state without relying on a single centralized controller for every update.
When should developers choose gossip coordination?
agent-gossip-coordinator fits large swarms needing horizontal scalability and tolerant eventual consistency. Choose it when peer-to-peer state fan-out and conflict resolution matter more than immediate strict ordering from one orchestrator.
Is Agent Gossip Coordinator safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.