Agent Gossip Coordinator
Orchestrate gossip-style epidemic dissemination and eventual consistency when you are designing or running multi-node agent or service meshes.
Overview
Agent Gossip Coordinator is an agent skill most often used in Build (also Operate) that coordinates gossip-based consensus for scalable, eventually consistent multi-node systems.
Install
npx skills add https://github.com/ruvnet/ruflo --skill agent-gossip-coordinatorWhat is this skill?
- Push and pull gossip protocols for epidemic information spread across peers
- Random peer selection, failure detection, and fanout tuning for bandwidth efficiency
- Vector-clock state sync with conflict resolution and convergence monitoring
- Pre/post shell hooks that initialize topology and log consistency cycle status
- Five core responsibilities from dissemination through scalability control
- 5 core coordinator responsibilities
- push and pull epidemic dissemination modes
Adoption & trust: 639 installs on skills.sh; 58.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need nodes to share state without a central coordinator, but ad-hoc broadcast or leader election will not scale with your agent mesh.
Who is it for?
Indie builders designing multi-agent or microservice meshes who want epidemic dissemination and vector-clock sync spelled out for their agent to implement.
Skip if: Single-process apps or teams that require strong synchronous consensus (e.g. strict linearizability) without eventual consistency tradeoffs.
When should I use this skill?
You are implementing or tuning gossip-based consensus, peer dissemination, or eventual consistency across distributed agent or service nodes.
What do I get? / Deliverables
You get a structured push/pull gossip workflow with peer selection, sync, and convergence checks so distributed nodes can reach eventual consistency with tunable fanout.
- Gossip cycle plan with fanout and peer-selection rules
- Hook-aligned runbook for pre/post coordination checks
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Gossip coordination is introduced while you are still architecting scalable backends and agent topologies, even though you keep tuning it after deploy. Backend is the canonical shelf because peer selection, vector clocks, and conflict resolution are infrastructure concerns under your API and worker layer.
Where it fits
Sketch push/pull gossip and peer fanout before coding your agent mesh state layer.
Align gossip cycles with MCP or HTTP peer hooks so workers see consistent task metadata.
Monitor convergence and bandwidth after deploy when node count grows.
Use post-hook convergence logging as a checklist for alerting on stuck partitions.
How it compares
Use as a coordination playbook for peer-to-peer state spread, not as a hosted message bus or managed Kafka replacement.
Common Questions / FAQ
Who is agent-gossip-coordinator for?
Solo and small-team builders wiring scalable agent or backend topologies who need gossip-style eventual consistency without drowning in distributed-systems papers.
When should I use agent-gossip-coordinator?
During Build when you design backend peer networks and agent coordination, and in Operate when you tune dissemination, detect failed peers, and monitor convergence after deploy.
Is agent-gossip-coordinator safe to install?
Review the Security Audits panel on this Prism page and inspect hook scripts in the repo; the skill references shell pre/post hooks that run in your environment.
Workflow Chain
Then invoke: agent worker specialist
SKILL.md
READMESKILL.md - Agent Gossip Coordinator
--- 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