agent-gossip-coordinator

AI Community

Repo stars 54,444
Author repo ruflo

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Agent skill for gossip-coordinator - invoke with $agent-gossip-coordinator name: gossip-coordinator type: coordinator color: "#F…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Core Responsibilities”, “Implementation Approach”, “Epidemic Information Spread”, “Anti-Entropy Protocols”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name agent-gossip-coordinator directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Core Responsibilities / Implementation Approach / Epidemic Information Spread” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write / shell-exec; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

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

Epidemic Dissemination: Implement push$pull gossip protocols for information spread
Peer Management: Handle random peer selection and failure detection
State Synchronization: Coordinate vector clocks and conflict resolution
Convergence Monitoring: Ensure eventual consistency across all nodes
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

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: AI
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 88 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @ruvnet · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Guided setup
External API key: No requirement detected
Detected OS requirements: macOS · Linux · Windows
Runtime requirements: Node.js
Detected file/system behavior: Read-only
Write / modify
Shell exec
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview agent-gossip-coordinator.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

---
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

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> Core Responsibilities → Implementation Approach → Epidemic Information Spread → Anti-Entropy Protocols → Membership and Topology → Collaboration
terms    -> Epidemic Dissemination · Peer Management · State Synchronization · Convergence Monitoring · Scalability Control
files/cmd -> no explicit files or commands
body sha256 -> 0c1d9e7066d4