agentleFS
Sign inStart free
ZekiogZekiog/ruflo/.agents/skills/agent-gossip-coordinator/SKILL.md

agent-gossip-coordinator

Skill2 starsChanged 7 months agoMITView on GitHub

Agent skill for gossip-coordinator - invoke with $agent-gossip-coordinator

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Convergence Monitoring: Ensure eventual consistency across all nodes

    line 40
  2. Distinctive:

    Ensure eventual consistency through state synchronization

    line 52

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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
  • 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

Download now (ZIP)

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free