agent-gossip-coordinator

Name: agent-gossip-coordinator
Author: ruvnet

AI Community

Repo stars 54,444
Author updated Live
Author repo ruflo

Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network

Domain: AI
Compatible agents: Claude Code
Cursor
Cline
Codex
Windsurf
Gemini CLI

+20
Trust score: 88 / 100 · community maintained
Author / version / license: @ruvnet · no license declared
Token usage: Lean
Setup complexity: Guided setup
External API key: Not required
Operating systems: macOS · Linux · Windows
Runtime requirements: Node.js
Permissions: Read-only
Write / modify
Shell exec
Network behavior: Local-only
Install commands: 26 variants

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

---
name: agent-gossip-coordinator
description: Agent skill for gossip-coordinator - invoke with $agent-gossip-coordinator name: gossip-coordina…
category: ai
runtime: Node.js
---

# agent-gossip-coordinator output preview

## PART A: Task fit
- Use case: 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 priority: medium runs entirely locally; runs on Node.js. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Core Responsibilities / Implementation Approach / Epidemic Information Spread” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “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 priority: medium runs entirely locally; runs on Node.js. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Core Responsibilities / Implementation Approach / Epidemic Information Spread” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.

SKILL.md SKILL.md

---
name: agent-gossip-coordinator
description: Agent skill for gossip-coordinator - invoke with $agent-gossip-coordinator name: gossip-coordina…
category: ai
source: ruvnet/ruflo
---

# agent-gossip-coordinator

## When to use
- Agent skill for gossip-coordinator - invoke with $agent-gossip-coordinator name: gossip-coordinator type: coordinator…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.

## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.

## Execution rules
- Organize steps around “Core Responsibilities / Implementation Approach / Epidemic Information Spread” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.

## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.

Evidence boundary and execution chain

The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.

skill "agent-gossip-coordinator" {
  input      -> user goal + target files + boundaries + acceptance criteria
  context    -> Core Responsibilities / Implementation Approach / Epidemic Information Spread
  rules      -> SKILL.md triggers / order / output contract
  runtime    -> Node.js | read files, write/modify files, run shell commands | mostly runs locally
  guardrails -> usually needs no extra API key + small-sample validation + diff/log review
  output     -> copyable result + checklist + next iteration
}

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

Install command

One-click installPick a runner, click Copy, paste into your terminal, press enter

npx skills add ruvnet/ruflo/.agents/skills/agent-gossip-coordinator -y

Open general install guide

View skill source

Works with

Claude Code
Cursor
Cline
Codex
Windsurf
Gemini
OpenCode
Roo Code
AAide
+Augment
GitHub Copilot
OpenClaw
KKiro
Junie
WWarp
Goose
Trae
Kilo Code
OpenHands
Amp
Zencoder
CContinue
AIAider
CodeBuddy
CodeGeeX
Replit Agent

Security audit

88 / 100

Community

未声明 license/许可。
未声明 version。
未限定 allowed-tools，默认拥有全部工具权限。

Metadata

Source: github
ruvnet/ruflo
中文

More by @ruvnet

Category & tags

Category AI