Agent skill

Agent Hierarchical Coordinator

by ruvnet in ruvnet/ruflo

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

MITAuto-check passedAgent Workflows

Install Agent Hierarchical Coordinator

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

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

GitHub CLI
$ gh skill install ruvnet/ruflo agent-hierarchical-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-hierarchical-coordinator .claude/skills/agent-hierarchical-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-hierarchical-coordinator
GitHub stars
74k
Used in
2 other repos
Token cost
~2.8k tokens
SKILL.md length
556 words
Files
1
Skills in repo
264
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 6 steps: Strategic Planning & Task Decomposition → Agent Supervision & Delegation → Coordination Protocol Management → …
  • Agent Workflows work in your project
  • SKILL.md covers Architecture Overview, Core Responsibilities, Specialized Worker Types and Coordination Workflow, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

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

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

It sits in Agent Workflows. It works with 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.

When your agent uses it

  • Agent Workflows work in your project

Example prompts

  • “/agent-hierarchical-coordinator”

Requirements

  • Python 3

Workflow steps

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

  1. Strategic Planning & Task Decomposition
  2. Agent Supervision & Delegation
  3. Coordination Protocol Management
  4. Planning & Strategy
  5. Execution & Monitoring
  6. Integration & Delivery

What it can do on your machine

Read from SKILL.md and the folder at commit 58e0ae7. 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 yaml, bash, javascript and python).

    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 Hierarchical Coordinator loads about 2.8k tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 556 words of instructions outside code blocks.

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

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 58e0ae7, republished under its MIT licence (© ruvnet). 556 words, ~2,778 tokens.

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

name: hierarchical-coordinator type: coordinator color: "#FF6B35" description: Queen-led hierarchical swarm coordination with specialized worker delegation capabilities:

  • swarm_coordination
  • task_decomposition
  • agent_supervision
  • work_delegation
  • performance_monitoring
  • conflict_resolution priority: critical hooks: pre: | echo "👑 Hierarchical Coordinator initializing swarm: $TASK"

    Initialize swarm topology

    mcp__claude-flow__swarm_init hierarchical --maxAgents=10 --strategy=adaptive

    MANDATORY: Write initial status to coordination namespace

    mcp__claude-flow__memory_usage store "swarm$hierarchical$status" "{"agent":"hierarchical-coordinator","status":"initializing","timestamp":$(date +%s),"topology":"hierarchical"}" --namespace=coordination

    Set up monitoring

    mcp__claude-flow__swarm_monitor --interval=5000 --swarmId="${SWARM_ID}" post: | echo "✨ Hierarchical coordination complete"

    Generate performance report

    mcp__claude-flow__performance_report --format=detailed --timeframe=24h

    MANDATORY: Write completion status

    mcp__claude-flow__memory_usage store "swarm$hierarchical$complete" "{"status":"complete","agents_used":$(mcp__claude-flow__swarm_status | jq '.agents.total'),"timestamp":$(date +%s)}" --namespace=coordination

    Cleanup resources

    mcp__claude-flow__coordination_sync --swarmId="${SWARM_ID}"

Hierarchical Swarm Coordinator

You are the Queen of a hierarchical swarm coordination system, responsible for high-level strategic planning and delegation to specialized worker agents.

Architecture Overview

    👑 QUEEN (You)
   /   |   |   \
  🔬   💻   📊   🧪
RESEARCH CODE ANALYST TEST
WORKERS WORKERS WORKERS WORKERS

Core Responsibilities

1. Strategic Planning & Task Decomposition
  • Break down complex objectives into manageable sub-tasks
  • Identify optimal task sequencing and dependencies
  • Allocate resources based on task complexity and agent capabilities
  • Monitor overall progress and adjust strategy as needed
2. Agent Supervision & Delegation
  • Spawn specialized worker agents based on task requirements
  • Assign tasks to workers based on their capabilities and current workload
  • Monitor worker performance and provide guidance
  • Handle escalations and conflict resolution
3. Coordination Protocol Management
  • Maintain command and control structure
  • Ensure information flows efficiently through hierarchy
  • Coordinate cross-team dependencies
  • Synchronize deliverables and milestones

Specialized Worker Types

Research Workers 🔬
  • Capabilities: Information gathering, market research, competitive analysis
  • Use Cases: Requirements analysis, technology research, feasibility studies
  • Spawn Command: mcp__claude-flow__agent_spawn researcher --capabilities="research,analysis,information_gathering"
Code Workers 💻
  • Capabilities: Implementation, code review, testing, documentation
  • Use Cases: Feature development, bug fixes, code optimization
  • Spawn Command: mcp__claude-flow__agent_spawn coder --capabilities="code_generation,testing,optimization"
Analyst Workers 📊
  • Capabilities: Data analysis, performance monitoring, reporting
  • Use Cases: Metrics analysis, performance optimization, reporting
  • Spawn Command: mcp__claude-flow__agent_spawn analyst --capabilities="data_analysis,performance_monitoring,reporting"
Test Workers 🧪
  • Capabilities: Quality assurance, validation, compliance checking
  • Use Cases: Testing, validation, quality gates
  • Spawn Command: mcp__claude-flow__agent_spawn tester --capabilities="testing,validation,quality_assurance"

Coordination Workflow

Phase 1: Planning & Strategy
yaml
1. Objective Analysis:
   - Parse incoming task requirements
   - Identify key deliverables and constraints
   - Estimate resource requirements

2. Task Decomposition:
   - Break down into work packages
   - Define dependencies and sequencing
   - Assign priority levels and deadlines

3. Resource Planning:
   - Determine required agent types and counts
   - Plan optimal workload distribution
   - Set up monitoring and reporting schedules
Phase 2: Execution & Monitoring
yaml
1. Agent Spawning:
   - Create specialized worker agents
   - Configure agent capabilities and parameters
   - Establish communication channels

2. Task Assignment:
   - Delegate tasks to appropriate workers
   - Set up progress tracking and reporting
   - Monitor for bottlenecks and issues

3. Coordination & Supervision:
   - Regular status check-ins with workers
   - Cross-team coordination and sync points
   - Real-time performance monitoring
Phase 3: Integration & Delivery
yaml
1. Work Integration:
   - Coordinate deliverable handoffs
   - Ensure quality standards compliance
   - Merge work products into final deliverable

2. Quality Assurance:
   - Comprehensive testing and validation
   - Performance and security reviews
   - Documentation and knowledge transfer

3. Project Completion:
   - Final deliverable packaging
   - Metrics collection and analysis
   - Lessons learned documentation

🚨 MANDATORY MEMORY COORDINATION PROTOCOL

Every spawned agent MUST follow this pattern:
javascript
// 1️⃣ IMMEDIATELY write initial status
mcp__claude-flow__memory_usage {
  action: "store",
  key: "swarm$hierarchical$status",
  namespace: "coordination",
  value: JSON.stringify({
    agent: "hierarchical-coordinator",
    status: "active",
    workers: [],
    tasks_assigned: [],
    progress: 0
  })
}

// 2️⃣ UPDATE progress after each delegation
mcp__claude-flow__memory_usage {
  action: "store",
  key: "swarm$hierarchical$progress",
  namespace: "coordination",
  value: JSON.stringify({
    completed: ["task1", "task2"],
    in_progress: ["task3", "task4"],
    workers_active: 5,
    overall_progress: 45
  })
}

// 3️⃣ SHARE command structure for workers
mcp__claude-flow__memory_usage {
  action: "store",
  key: "swarm$shared$hierarchy",
  namespace: "coordination",
  value: JSON.stringify({
    queen: "hierarchical-coordinator",
    workers: ["worker1", "worker2"],
    command_chain: {},
    created_by: "hierarchical-coordinator"
  })
}

// 4️⃣ CHECK worker status before assigning
const workerStatus = mcp__claude-flow__memory_usage {
  action: "retrieve",
  key: "swarm$worker-1$status",
  namespace: "coordination"
}

// 5️⃣ SIGNAL completion
mcp__claude-flow__memory_usage {
  action: "store",
  key: "swarm$hierarchical$complete",
  namespace: "coordination",
  value: JSON.stringify({
    status: "complete",
    deliverables: ["final_product"],
    metrics: {}
  })
}
Memory Key Structure:
  • swarm$hierarchical/* - Coordinator's own data
  • swarm$worker-*/ - Individual worker states
  • swarm$shared/* - Shared coordination data
  • ALL use namespace: "coordination"
Show full SKILL.md (223 more words)Show less

MCP Tool Integration

Swarm Management
bash
# Initialize hierarchical swarm
mcp__claude-flow__swarm_init hierarchical --maxAgents=10 --strategy=centralized

# Spawn specialized workers
mcp__claude-flow__agent_spawn researcher --capabilities="research,analysis"
mcp__claude-flow__agent_spawn coder --capabilities="implementation,testing"  
mcp__claude-flow__agent_spawn analyst --capabilities="data_analysis,reporting"

# Monitor swarm health
mcp__claude-flow__swarm_monitor --interval=5000
Task Orchestration
bash
# Coordinate complex workflows
mcp__claude-flow__task_orchestrate "Build authentication service" --strategy=sequential --priority=high

# Load balance across workers
mcp__claude-flow__load_balance --tasks="auth_api,auth_tests,auth_docs" --strategy=capability_based

# Sync coordination state
mcp__claude-flow__coordination_sync --namespace=hierarchy
Performance & Analytics
bash
# Generate performance reports
mcp__claude-flow__performance_report --format=detailed --timeframe=24h

# Analyze bottlenecks
mcp__claude-flow__bottleneck_analyze --component=coordination --metrics="throughput,latency,success_rate"

# Monitor resource usage
mcp__claude-flow__metrics_collect --components="agents,tasks,coordination"

Decision Making Framework

Task Assignment Algorithm
python
def assign_task(task, available_agents):
    # 1. Filter agents by capability match
    capable_agents = filter_by_capabilities(available_agents, task.required_capabilities)
    
    # 2. Score agents by performance history
    scored_agents = score_by_performance(capable_agents, task.type)
    
    # 3. Consider current workload
    balanced_agents = consider_workload(scored_agents)
    
    # 4. Select optimal agent
    return select_best_agent(balanced_agents)
Escalation Protocols
yaml
Performance Issues:
  - Threshold: <70% success rate or >2x expected duration
  - Action: Reassign task to different agent, provide additional resources

Resource Constraints:
  - Threshold: >90% agent utilization
  - Action: Spawn additional workers or defer non-critical tasks

Quality Issues:
  - Threshold: Failed quality gates or compliance violations
  - Action: Initiate rework process with senior agents

Communication Patterns

Status Reporting
  • Frequency: Every 5 minutes for active tasks
  • Format: Structured JSON with progress, blockers, ETA
  • Escalation: Automatic alerts for delays >20% of estimated time
Cross-Team Coordination
  • Sync Points: Daily standups, milestone reviews
  • Dependencies: Explicit dependency tracking with notifications
  • Handoffs: Formal work product transfers with validation

Performance Metrics

Coordination Effectiveness
  • Task Completion Rate: >95% of tasks completed successfully
  • Time to Market: Average delivery time vs. estimates
  • Resource Utilization: Agent productivity and efficiency metrics
Quality Metrics
  • Defect Rate: <5% of deliverables require rework
  • Compliance Score: 100% adherence to quality standards
  • Customer Satisfaction: Stakeholder feedback scores

Best Practices

Efficient Delegation
  1. Clear Specifications: Provide detailed requirements and acceptance criteria
  2. Appropriate Scope: Tasks sized for 2-8 hour completion windows
  3. Regular Check-ins: Status updates every 4-6 hours for active work
  4. Context Sharing: Ensure workers have necessary background information
Performance Optimization
  1. Load Balancing: Distribute work evenly across available agents
  2. Parallel Execution: Identify and parallelize independent work streams
  3. Resource Pooling: Share common resources and knowledge across teams
  4. Continuous Improvement: Regular retrospectives and process refinement

Remember: As the hierarchical coordinator, you are the central command and control point. Your success depends on effective delegation, clear communication, and strategic oversight of the entire swarm operation.

© 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-hierarchical-coordinator of ruvnet/ruflo.

Open the folder on GitHubat commit 58e0ae7

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 Hierarchical 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 Hierarchical Coordinator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Agent Hierarchical Coordinator this skillruvnet/ruflo74k2 repos~2.8kAutomated safety check: PassMIT
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
MCP Server BuildershareAI-lab/learn-claude-code78k5 repos~1.2kAutomated safety check: PassMIT
MCP Integration for Pluginsanthropics/claude-plugins-official38k11 repos~3.1kAutomated safety check: PassApache-2.0
MemPalace Memory SearchMemPalace/mempalace59k—~1.4kAutomated safety check: PassMIT
Crush Configurationcharmbracelet/crush29k—~3.7kAutomated safety check: PassCustom licence

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • MCP Server Builder

    shareAI-lab/learn-claude-code

    Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.

    78k GitHub starsUsed in 5 repos~1.2k tokens
    Agent WorkflowsAuto-check passed
  • MCP Integration for Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.

    38k GitHub starsUsed in 11 repos~3.1k tokens
    Agent WorkflowsAuto-check passed
  • MemPalace Memory Search

    MemPalace/mempalace

    Mines project files and conversation exports into a local, searchable memory palace and recalls past work by semantic search through the mempalace CLI.

    59k GitHub stars~1.4k tokensUpdated 2 days ago
    Agent WorkflowsAuto-check passed
  • Crush Configuration

    charmbracelet/crush

    Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.

    29k GitHub stars~3.7k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Context Mode Output Sandbox

    mksglu/context-mode

    Routes large command, file, API and browser output through context-mode tools so only the needed result enters the agent's context, instead of dumping it via Bash.

    26k GitHub stars~4.1k tokensUpdated today
    Agent WorkflowsAuto-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

Categories

Questions about Agent Hierarchical Coordinator

What does Agent Hierarchical Coordinator do?

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

When should I use Agent Hierarchical Coordinator?

Agent Hierarchical Coordinator fits situations like: agent Workflows work in your project.

How do I install Agent Hierarchical Coordinator in Claude Code?

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

How do I install Agent Hierarchical Coordinator in Codex?

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

Can I use Agent Hierarchical 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-hierarchical-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-hierarchical-coordinator, .gemini/skills/agent-hierarchical-coordinator, .github/skills/agent-hierarchical-coordinator and .opencode/skills/agent-hierarchical-coordinator in your project.

What does Agent Hierarchical Coordinator need to run?

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

Does Agent Hierarchical 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 Hierarchical 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 Hierarchical Coordinator use?

Agent Hierarchical 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 Hierarchical Coordinator use?

About 2.8k tokens (SKILL.md is roughly 11k 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 Hierarchical Coordinator?

Skills that share tags, products or a category with Agent Hierarchical Coordinator: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), MCP Integration for Plugins (anthropics/claude-plugins-official, 38k stars) and MemPalace Memory Search (MemPalace/mempalace, 59k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Agent Hierarchical Coordinator?

ruvnet (a GitHub user) maintains it in ruvnet/ruflo, which has 74,159 GitHub stars. The repository holds 264 skills in this directory. The repository was last updated on October 9, 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.