home / skills / ruvnet / ruflo / agent-gossip-coordinator

agent-gossip-coordinator skill

safe

/.agents/skills/agent-gossip-coordinator

This skill coordinates gossip-based consensus to ensure scalable, eventual consistency across distributed systems, improving data freshness and fault tolerance.

npx playbooks add skill ruvnet/ruflo --skill agent-gossip-coordinator

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.5 KB

---
name: agent-gossip-coordinator
description: Agent skill for gossip-coordinator - invoke with $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

Overview

This skill coordinates gossip-based consensus protocols for scalable, eventually consistent distributed systems. It provides epidemic dissemination, peer selection, state synchronization, and conflict resolution primitives tailored for multi-node swarms. Designed for integration with agent orchestration platforms, it focuses on efficient, fault-tolerant information propagation and convergence monitoring.

How this skill works

The coordinator runs push, pull, and hybrid push-pull gossip routines to spread updates quickly while minimizing bandwidth. It manages peer selection and failure detection, compares node states using anti-entropy techniques (e.g., Merkle trees, vector clocks), and applies deterministic conflict resolution to reconcile concurrent updates. The skill exposes hooks for lifecycle events and integrates with performance, CRDT, quorum, and security components to tune fanout, monitor convergence, and secure peer channels.

When to use it

You need scalable eventual consistency across a large, dynamic cluster
Fast, probabilistic dissemination of updates is required with constrained bandwidth
Systems tolerate temporary divergence but require eventual convergence
You need peer failure detection and seamless membership handling
Coordinating autonomous agents that must share state without strong global locking

Best practices

Use hybrid push-pull for balanced latency and bandwidth efficiency
Maintain vector clocks or CRDTs for causal tracking to simplify conflict resolution
Tune fanout and gossip interval based on observed node churn and network conditions
Run anti-entropy (Merkle tree) scans periodically to detect and repair drift
Integrate with a security manager to authenticate peers and encrypt gossip traffic

Example use cases

Replicating configuration or presence state across hundreds of agent nodes
Distributing critical notifications in an edge swarm where intermittent connectivity occurs
Synchronizing partially replicated caches in a multi-region deployment
Coordinating autonomous agent workflows that exchange small state deltas frequently
Implementing lightweight membership and failure detection for fault-tolerant services

FAQ

How does conflict resolution work in this coordinator?

It uses vector clocks and deterministic resolution policies, and can delegate conflict-free logic to CRDT synchronizers for application-specific merges.

Can it handle high node churn and network partitions?

Yes. It tunes fanout and gossip frequency to accommodate churn and relies on anti-entropy and eventual consistency to converge after partitions heal.