Agent skill

Agent Sync Coordinator

by ruvnet in ruvnet/ruflo

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

MITAuto-check passed

Install Agent Sync Coordinator

skills CLI
$ npx skills add ruvnet/ruflo --skill agent-sync-coordinator -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ruvnet/ruflo agent-sync-coordinator --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ruvnet/ruflo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/agent-sync-coordinator .claude/skills/agent-sync-coordinator && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
agent-sync-coordinator
GitHub stars
74k
Used in
2 other repos
Token cost
~4k tokens
SKILL.md length
372 words
Files
1
Skills in repo
264
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 10 steps: Synchronize Package Dependencies → Documentation Synchronization → Cross-Package Feature Integration → …
  • SKILL.md covers Purpose, Capabilities, Tools Available and Usage Patterns, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Agent Sync Coordinator is an agent skill from ruvnet/ruflo. Agent skill for sync-coordinator - invoke with $agent-sync-coordinator

Its SKILL.md is about 4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with GitHub and Model Context Protocol. The repository describes itself as: 🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory…. The licence is MIT.

Example prompts

  • “/agent-sync-coordinator”

Requirements

  • Node.js

Workflow steps

10 steps, taken from the step headings in SKILL.md.

  1. Synchronize Package Dependencies
  2. Documentation Synchronization
  3. Cross-Package Feature Integration
  4. Version Alignment Strategy
  5. Documentation Sync Pattern
  6. Integration Testing Matrix
  7. Atomic Synchronization
  8. Version Management
  9. Documentation Consistency
  10. Testing Integration

What it can do on your machine

Read from SKILL.md and the folder at commit de590e1. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are javascript and bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Agent Sync Coordinator loads about 4k tokens when it runs. Until then it costs about 23 tokens; SKILL.md has 372 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~23
When it runs · the whole SKILL.md, loaded when a task matches
~4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ruvnet/ruflo at commit de590e1, republished under its MIT licence (© ruvnet). 372 words, ~4,050 tokens.

Download SKILL.mdSave it as .claude/skills/agent-sync-coordinator/SKILL.md (or your agent's skills folder).
name
agent-sync-coordinator
description
Agent skill for sync-coordinator - invoke with $agent-sync-coordinator

name: sync-coordinator description: Multi-repository synchronization coordinator that manages version alignment, dependency synchronization, and cross-package integration with intelligent swarm orchestration type: coordination color: "#9B59B6" tools:

  • mcp__github__push_files
  • mcp__github__create_or_update_file
  • mcp__github__get_file_contents
  • mcp__github__create_pull_request
  • mcp__github__search_repositories
  • mcp__github__list_repositories
  • mcp__claude-flow__swarm_init
  • mcp__claude-flow__agent_spawn
  • mcp__claude-flow__task_orchestrate
  • mcp__claude-flow__memory_usage
  • mcp__claude-flow__coordination_sync
  • mcp__claude-flow__load_balance
  • TodoWrite
  • TodoRead
  • Bash
  • Read
  • Write
  • Edit
  • MultiEdit hooks: pre:
    • "Initialize multi-repository synchronization swarm with hierarchical coordination"
    • "Analyze package dependencies and version compatibility across all repositories"
    • "Store synchronization state and conflict detection in swarm memory" post:
    • "Validate synchronization success across all coordinated repositories"
    • "Update package documentation with synchronization status and metrics"
    • "Generate comprehensive synchronization report with recommendations"

GitHub Sync Coordinator

Purpose

Multi-package synchronization and version alignment with ruv-swarm coordination for seamless integration between claude-code-flow and ruv-swarm packages through intelligent multi-agent orchestration.

Capabilities

  • Package synchronization with intelligent dependency resolution
  • Version alignment across multiple repositories
  • Cross-package integration with automated testing
  • Documentation synchronization for consistent user experience
  • Release coordination with automated deployment pipelines

Tools Available

  • mcp__github__push_files
  • mcp__github__create_or_update_file
  • mcp__github__get_file_contents
  • mcp__github__create_pull_request
  • mcp__github__search_repositories
  • mcp__claude-flow__* (all swarm coordination tools)
  • TodoWrite, TodoRead, Task, Bash, Read, Write, Edit, MultiEdit

Usage Patterns

1. Synchronize Package Dependencies
javascript
// Initialize sync coordination swarm
mcp__claude-flow__swarm_init { topology: "hierarchical", maxAgents: 5 }
mcp__claude-flow__agent_spawn { type: "coordinator", name: "Sync Coordinator" }
mcp__claude-flow__agent_spawn { type: "analyst", name: "Dependency Analyzer" }
mcp__claude-flow__agent_spawn { type: "coder", name: "Integration Developer" }
mcp__claude-flow__agent_spawn { type: "tester", name: "Validation Engineer" }

// Analyze current package states
Read("$workspaces$ruv-FANN$claude-code-flow$claude-code-flow$package.json")
Read("$workspaces$ruv-FANN$ruv-swarm$npm$package.json")

// Synchronize versions and dependencies using gh CLI
// First create branch
Bash("gh api repos/:owner/:repo$git$refs -f ref='refs$heads$sync$package-alignment' -f sha=$(gh api repos/:owner/:repo$git$refs$heads$main --jq '.object.sha')")

// Update file using gh CLI
Bash(`gh api repos/:owner/:repo$contents$claude-code-flow$claude-code-flow$package.json \
  --method PUT \
  -f message="feat: Align Node.js version requirements across packages" \
  -f branch="sync$package-alignment" \
  -f content="$(echo '{ updated package.json with aligned versions }' | base64)" \
  -f sha="$(gh api repos/:owner/:repo$contents$claude-code-flow$claude-code-flow$package.json?ref=sync$package-alignment --jq '.sha')")`)

// Orchestrate validation
mcp__claude-flow__task_orchestrate {
  task: "Validate package synchronization and run integration tests",
  strategy: "parallel",
  priority: "high"
}
2. Documentation Synchronization
javascript
// Synchronize CLAUDE.md files across packages using gh CLI
// Get file contents
CLAUDE_CONTENT=$(Bash("gh api repos/:owner/:repo$contents$ruv-swarm$docs/CLAUDE.md --jq '.content' | base64 -d"))

// Update claude-code-flow CLAUDE.md to match using gh CLI
// Create or update branch
Bash("gh api repos/:owner/:repo$git$refs -f ref='refs$heads$sync$documentation' -f sha=$(gh api repos/:owner/:repo$git$refs$heads$main --jq '.object.sha') 2>$dev$null || gh api repos/:owner/:repo$git$refs$heads$sync$documentation --method PATCH -f sha=$(gh api repos/:owner/:repo$git$refs$heads$main --jq '.object.sha')")

// Update file
Bash(`gh api repos/:owner/:repo$contents$claude-code-flow$claude-code-flow/CLAUDE.md \
  --method PUT \
  -f message="docs: Synchronize CLAUDE.md with ruv-swarm integration patterns" \
  -f branch="sync$documentation" \
  -f content="$(echo '# Claude Code Configuration for ruv-swarm\n\n[synchronized content]' | base64)" \
  -f sha="$(gh api repos/:owner/:repo$contents$claude-code-flow$claude-code-flow/CLAUDE.md?ref=sync$documentation --jq '.sha' 2>$dev$null || echo '')")`)

// Store sync state in memory
mcp__claude-flow__memory_usage {
  action: "store",
  key: "sync$documentation$status",
  value: { timestamp: Date.now(), status: "synchronized", files: ["CLAUDE.md"] }
}
3. Cross-Package Feature Integration
javascript
// Coordinate feature implementation across packages
mcp__github__push_files {
  owner: "ruvnet",
  repo: "ruv-FANN",
  branch: "feature$github-commands",
  files: [
    {
      path: "claude-code-flow$claude-code-flow/.claude$commands$github$github-modes.md",
      content: "[GitHub modes documentation]"
    },
    {
      path: "claude-code-flow$claude-code-flow/.claude$commands$github$pr-manager.md", 
      content: "[PR manager documentation]"
    },
    {
      path: "ruv-swarm$npm$src$github-coordinator$claude-hooks.js",
      content: "[GitHub coordination hooks]"
    }
  ],
  message: "feat: Add comprehensive GitHub workflow integration"
}

// Create coordinated pull request using gh CLI
Bash(`gh pr create \
  --repo :owner/:repo \
  --title "Feature: GitHub Workflow Integration with Swarm Coordination" \
  --head "feature$github-commands" \
  --base "main" \
  --body "## 🚀 GitHub Workflow Integration

### Features Added
- ✅ Comprehensive GitHub command modes
- ✅ Swarm-coordinated PR management  
- ✅ Automated issue tracking
- ✅ Cross-package synchronization

### Integration Points
- Claude-code-flow: GitHub command modes in .claude$commands$github/
- ruv-swarm: GitHub coordination hooks and utilities
- Documentation: Synchronized CLAUDE.md instructions

### Testing
- [x] Package dependency verification
- [x] Integration test suite
- [x] Documentation validation
- [x] Cross-package compatibility

### Swarm Coordination
This integration uses ruv-swarm agents for:
- Multi-agent GitHub workflow management
- Automated testing and validation
- Progress tracking and coordination
- Memory-based state management

---
🤖 Generated with Claude Code using ruv-swarm coordination`
}

Batch Synchronization Example

Complete Package Sync Workflow:
javascript
[Single Message - Complete Synchronization]:
  // Initialize comprehensive sync swarm
  mcp__claude-flow__swarm_init { topology: "mesh", maxAgents: 6 }
  mcp__claude-flow__agent_spawn { type: "coordinator", name: "Master Sync Coordinator" }
  mcp__claude-flow__agent_spawn { type: "analyst", name: "Package Analyzer" }
  mcp__claude-flow__agent_spawn { type: "coder", name: "Integration Coder" }
  mcp__claude-flow__agent_spawn { type: "tester", name: "Validation Tester" }
  mcp__claude-flow__agent_spawn { type: "reviewer", name: "Quality Reviewer" }
  
  // Read current state of both packages
  Read("$workspaces$ruv-FANN$claude-code-flow$claude-code-flow$package.json")
  Read("$workspaces$ruv-FANN$ruv-swarm$npm$package.json")
  Read("$workspaces$ruv-FANN$claude-code-flow$claude-code-flow/CLAUDE.md")
  Read("$workspaces$ruv-FANN$ruv-swarm$docs/CLAUDE.md")
  
  // Synchronize multiple files simultaneously
  mcp__github__push_files {
    branch: "sync$complete-integration",
    files: [
      { path: "claude-code-flow$claude-code-flow$package.json", content: "[aligned package.json]" },
      { path: "claude-code-flow$claude-code-flow/CLAUDE.md", content: "[synchronized CLAUDE.md]" },
      { path: "claude-code-flow$claude-code-flow/.claude$commands$github$github-modes.md", content: "[GitHub modes]" }
    ],
    message: "feat: Complete package synchronization with GitHub integration"
  }
  
  // Run validation tests
  Bash("cd $workspaces$ruv-FANN$claude-code-flow$claude-code-flow && npm install")
  Bash("cd $workspaces$ruv-FANN$claude-code-flow$claude-code-flow && npm test")
  Bash("cd $workspaces$ruv-FANN$ruv-swarm$npm && npm test")
  
  // Track synchronization progress
  TodoWrite { todos: [
    { id: "sync-deps", content: "Synchronize package dependencies", status: "completed", priority: "high" },
    { id: "sync-docs", content: "Align documentation", status: "completed", priority: "medium" },
    { id: "sync-github", content: "Add GitHub command integration", status: "completed", priority: "high" },
    { id: "sync-test", content: "Validate synchronization", status: "completed", priority: "medium" },
    { id: "sync-pr", content: "Create integration PR", status: "pending", priority: "high" }
  ]}
  
  // Store comprehensive sync state
  mcp__claude-flow__memory_usage {
    action: "store",
    key: "sync$complete$status",
    value: {
      timestamp: Date.now(),
      packages_synced: ["claude-code-flow", "ruv-swarm"],
      version_alignment: "completed",
      documentation_sync: "completed",
      github_integration: "completed",
      validation_status: "passed"
    }
  }

Synchronization Strategies

1. Version Alignment Strategy
javascript
// Intelligent version synchronization
const syncStrategy = {
  nodeVersion: ">=20.0.0",  // Align to highest requirement
  dependencies: {
    "better-sqlite3": "^12.2.0",  // Use latest stable
    "ws": "^8.14.2"  // Maintain compatibility
  },
  engines: {
    aligned: true,
    strategy: "highest_common"
  }
}
2. Documentation Sync Pattern
javascript
// Keep documentation consistent across packages
const docSyncPattern = {
  sourceOfTruth: "ruv-swarm$docs/CLAUDE.md",
  targets: [
    "claude-code-flow$claude-code-flow/CLAUDE.md",
    "CLAUDE.md"  // Root level
  ],
  customSections: {
    "claude-code-flow": "GitHub Commands Integration",
    "ruv-swarm": "MCP Tools Reference"
  }
}
3. Integration Testing Matrix
javascript
// Comprehensive testing across synchronized packages
const testMatrix = {
  packages: ["claude-code-flow", "ruv-swarm"],
  tests: [
    "unit_tests",
    "integration_tests", 
    "cross_package_tests",
    "mcp_integration_tests",
    "github_workflow_tests"
  ],
  validation: "parallel_execution"
}

Best Practices

1. Atomic Synchronization
  • Use batch operations for related changes
  • Maintain consistency across all sync operations
  • Implement rollback mechanisms for failed syncs
Show full SKILL.md (150 more words)Show less
2. Version Management
  • Semantic versioning alignment
  • Dependency compatibility validation
  • Automated version bump coordination
3. Documentation Consistency
  • Single source of truth for shared concepts
  • Package-specific customizations
  • Automated documentation validation
4. Testing Integration
  • Cross-package test validation
  • Integration test automation
  • Performance regression detection

Monitoring and Metrics

Sync Quality Metrics:
  • Package version alignment percentage
  • Documentation consistency score
  • Integration test success rate
  • Synchronization completion time
Automated Reporting:
  • Weekly sync status reports
  • Dependency drift detection
  • Documentation divergence alerts
  • Integration health monitoring

Advanced Swarm Synchronization Features

Multi-Agent Coordination Architecture
bash
# Initialize comprehensive synchronization swarm
mcp__claude-flow__swarm_init { topology: "hierarchical", maxAgents: 10 }
mcp__claude-flow__agent_spawn { type: "coordinator", name: "Master Sync Coordinator" }
mcp__claude-flow__agent_spawn { type: "analyst", name: "Dependency Analyzer" }
mcp__claude-flow__agent_spawn { type: "coder", name: "Integration Developer" }
mcp__claude-flow__agent_spawn { type: "tester", name: "Validation Engineer" }
mcp__claude-flow__agent_spawn { type: "reviewer", name: "Quality Assurance" }
mcp__claude-flow__agent_spawn { type: "monitor", name: "Sync Monitor" }

# Orchestrate complex synchronization workflow
mcp__claude-flow__task_orchestrate {
  task: "Execute comprehensive multi-repository synchronization with validation",
  strategy: "adaptive",
  priority: "critical",
  dependencies: ["version_analysis", "dependency_resolution", "integration_testing"]
}

# Load balance synchronization tasks across agents
mcp__claude-flow__load_balance {
  swarmId: "sync-coordination-swarm",
  tasks: [
    "package_json_sync",
    "documentation_alignment", 
    "version_compatibility_check",
    "integration_test_execution"
  ]
}
Intelligent Conflict Resolution
javascript
// Advanced conflict detection and resolution
const syncConflictResolver = async (conflicts) => {
  // Initialize conflict resolution swarm
  await mcp__claude_flow__swarm_init({ topology: "mesh", maxAgents: 6 });
  
  // Spawn specialized conflict resolution agents
  await mcp__claude_flow__agent_spawn({ type: "analyst", name: "Conflict Analyzer" });
  await mcp__claude_flow__agent_spawn({ type: "coder", name: "Resolution Developer" });
  await mcp__claude_flow__agent_spawn({ type: "reviewer", name: "Solution Validator" });
  
  // Store conflict context in swarm memory
  await mcp__claude_flow__memory_usage({
    action: "store",
    key: "sync$conflicts$current",
    value: {
      conflicts,
      resolution_strategy: "automated_with_validation",
      priority_order: conflicts.sort((a, b) => b.impact - a.impact)
    }
  });
  
  // Coordinate conflict resolution workflow
  return await mcp__claude_flow__task_orchestrate({
    task: "Resolve synchronization conflicts with multi-agent validation",
    strategy: "sequential",
    priority: "high"
  });
};
Comprehensive Synchronization Metrics
bash
# Store detailed synchronization metrics
mcp__claude-flow__memory_usage {
  action: "store",
  key: "sync$metrics$session",
  value: {
    packages_synchronized: ["claude-code-flow", "ruv-swarm"],
    version_alignment_score: 98.5,
    dependency_conflicts_resolved: 12,
    documentation_sync_percentage: 100,
    integration_test_success_rate: 96.8,
    total_sync_time: "23.4 minutes",
    agent_efficiency_scores: {
      "Master Sync Coordinator": 9.2,
      "Dependency Analyzer": 8.7,
      "Integration Developer": 9.0,
      "Validation Engineer": 8.9
    }
  }
}

Error Handling and Recovery

Swarm-Coordinated Error Recovery
bash
# Initialize error recovery swarm
mcp__claude-flow__swarm_init { topology: "star", maxAgents: 5 }
mcp__claude-flow__agent_spawn { type: "monitor", name: "Error Monitor" }
mcp__claude-flow__agent_spawn { type: "analyst", name: "Failure Analyzer" }
mcp__claude-flow__agent_spawn { type: "coder", name: "Recovery Developer" }

# Coordinate recovery procedures
mcp__claude-flow__coordination_sync { swarmId: "error-recovery-swarm" }

# Store recovery state
mcp__claude-flow__memory_usage {
  action: "store",
  key: "sync$recovery$state",
  value: {
    error_type: "version_conflict",
    recovery_strategy: "incremental_rollback",
    agent_assignments: {
      "conflict_resolution": "Recovery Developer",
      "validation": "Failure Analyzer",
      "monitoring": "Error Monitor"
    }
  }
}
Automatic handling of:
  • Version conflict resolution with swarm consensus
  • Merge conflict detection and multi-agent resolution
  • Test failure recovery with adaptive strategies
  • Documentation sync conflicts with intelligent merging
Recovery procedures:
  • Swarm-coordinated automated rollback on critical failures
  • Multi-agent incremental sync retry mechanisms
  • Intelligent intervention points for complex conflicts
  • Persistent state preservation across sync operations with memory coordination

© ruvnet, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/agent-sync-coordinator of ruvnet/ruflo.

Open the folder on GitHubat commit de590e1

Used in 2 other repositories

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in ruvnet/ruflo, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Agent Sync Coordinator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Agent Sync Coordinator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Agent Sync Coordinator this skillruvnet/ruflo74k2 repos~4kAutomated safety check: PassMIT
ComposioComposioHQ/composio30k1 repos~1.7kAutomated safety check: PassMIT
Skill Seekers Builderyusufkaraaslan/Skill_Seekers15k—~760Automated safety check: PassMIT
Library Documentation Seekerwithkynam/vibecode-pro-max-kit1.1k2 repos~1kAutomated safety check: NotesMIT
GraphifyEBISPOT/ols41046 repos~9.5kAutomated safety check: PassApache-2.0
GitDiagram Repository Overviewahmedkhaleel2004/gitdiagram18k—~427Automated safety check: PassMIT

Similar skills

  • Composio

    ComposioHQ/composio

    Route and complete Composio work across Composio For You and Composio Platform.

    30k GitHub starsUsed in 1 repo~1.7k tokens
    Productivity & AutomationAuto-check passed
  • Skill Seekers Builder

    yusufkaraaslan/Skill_Seekers

    Detects the type of a knowledge source and uses the Skill Seekers MCP tools to turn docs, repos, PDFs or videos into packaged AI skills.

    15k GitHub stars~760 tokensUpdated 7 days ago
    Agent WorkflowsAuto-check passed
  • Library Documentation Seeker

    withkynam/vibecode-pro-max-kit

    Looks up library and framework documentation through Context7 first, with bundled Node scripts as a fallback that fetch and analyze llms.txt files.

    1.1k GitHub starsUsed in 2 repos~1k tokens
    DevelopmentAuto-check: notes
  • Graphify

    EBISPOT/ols4

    A skill your agent uses for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a…

    104 GitHub starsUsed in 6 repos~9.5k tokens
    Knowledge ManagementAuto-check passed
  • GitDiagram Repository Overview

    ahmedkhaleel2004/gitdiagram

    Explains the architecture of a public GitHub repository through GitDiagram: how the code is organized, the main components with paths, and a Mermaid diagram.

    18k GitHub stars~427 tokensUpdated today
    DevelopmentAuto-check passed
  • Herdr Issue Triage

    herdrdev/herdr

    Triages open herdr GitHub issues into a short decision-first Markdown table with a priority light, recommendation, age, reactions and a reason for each.

    43k GitHub stars~517 tokensUpdated today
    DevelopmentAuto-check passed

More from ruvnet/ruflo

All 264 skills in this repo
  • Stores, searches, and retrieves successful patterns with HNSW-indexed semantic search so agents can reuse past solutions instead of relearning them.

    74k GitHub starsUsed in 2 repos~830 tokens
    Auto-check passed
  • Runs claude-flow CLI security scans for input validation, path traversal, SQL injection, XSS, hardcoded secrets and known CVEs, and writes an audit report.

    74k GitHub starsUsed in 2 repos~823 tokens
    Auto-check passed
  • Applies the SPARC method (specification, pseudocode, architecture, refinement, completion) with 17 specialized modes and multi-agent orchestration, from research to deployment.

    74k GitHub starsUsed in 2 repos~829 tokens
    Auto-check passed
  • Coordinates a hierarchical swarm of specialized agents through the claude-flow CLI for work that spans several files or modules at once.

    74k GitHub starsUsed in 2 repos~779 tokens
    Auto-check passed
  • Sets up and drives Ruflo, an npm-installed orchestration layer for multi-agent swarms, persistent memory, routing, hooks and its MCP tool catalog.

    74k GitHub starsUsed in 1 repo~975 tokens
    Auto-check passed
  • Agent Coordination

    ruvnet/ruflo

    Reference for spawning, listing, monitoring and stopping agents with claude-flow commands, with agent type families, routing codes and coordination tips.

    74k GitHub starsUsed in 2 repos~519 tokens
    Auto-check passed

Questions about Agent Sync Coordinator

What does Agent Sync Coordinator do?

Agent skill for sync-coordinator - invoke with $agent-sync-coordinator. Agent Sync Coordinator is an agent skill from ruvnet/ruflo.

How do I install Agent Sync Coordinator in Claude Code?

Run `npx skills add ruvnet/ruflo --skill agent-sync-coordinator -a claude-code`. Or copy the skill folder (.agents/skills/agent-sync-coordinator in ruvnet/ruflo) into .claude/skills/agent-sync-coordinator in your project. Claude Code loads it when a task matches its description.

How do I install Agent Sync Coordinator in Codex?

Run `npx skills add ruvnet/ruflo --skill agent-sync-coordinator -a codex`. Or copy the skill folder (.agents/skills/agent-sync-coordinator in ruvnet/ruflo) into .agents/skills/agent-sync-coordinator in your project. Codex loads it when a task matches its description.

Can I use Agent Sync Coordinator in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ruvnet/ruflo --skill agent-sync-coordinator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/agent-sync-coordinator, .gemini/skills/agent-sync-coordinator, .github/skills/agent-sync-coordinator and .opencode/skills/agent-sync-coordinator in your project.

What does Agent Sync Coordinator need to run?

SKILL.md names no scripts, command-line tools or credentials: Agent Sync Coordinator is instructions for the agent only. Our summary lists: Node.js.

Does Agent Sync Coordinator access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Agent Sync Coordinator safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Agent Sync Coordinator use?

Agent Sync Coordinator is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Agent Sync Coordinator use?

About 4k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Agent Sync Coordinator?

Skills that share tags, products or a category with Agent Sync Coordinator: Composio (ComposioHQ/composio, 30k stars), Skill Seekers Builder (yusufkaraaslan/Skill_Seekers, 15k stars), Library Documentation Seeker (withkynam/vibecode-pro-max-kit, 1.1k stars) and Graphify (EBISPOT/ols4, 104 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Agent Sync Coordinator?

ruvnet (a GitHub user) maintains it in ruvnet/ruflo, which has 74,012 GitHub stars. The repository holds 264 skills in this directory. The repository was last updated on October 7, 2026.

Source: ruvnet/ruflo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.