Agent skill

Agent Orchestrator Task

by ruvnet in ruvnet/ruflo

Agent skill for orchestrator-task - invoke with $agent-orchestrator-task

MITAuto-check passedAgent Workflows

Install Agent Orchestrator Task

skills CLI
$ npx skills add ruvnet/ruflo --skill agent-orchestrator-task -a claude-code

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

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

At a glance

Agent skill for orchestrator-task - invoke with $agent-orchestrator-task

  • Works in 10 steps: Task Decomposition → Execution Strategy → Progress Management → …
  • Tasks that involve Multi-agent orchestration
  • SKILL.md covers Purpose, Core Functionality, Usage Examples and Task Patterns, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Agent Orchestrator Task is an agent skill from ruvnet/ruflo. Agent skill for orchestrator-task - invoke with $agent-orchestrator-task

Its SKILL.md is about 1k 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, covering Multi-agent orchestration and Task breakdown. 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

  • Tasks that involve Multi-agent orchestration
  • Tasks that involve Task breakdown

Example prompts

  • “/agent-orchestrator-task”

Workflow steps

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

  1. Task Decomposition
  2. Execution Strategy
  3. Progress Management
  4. Result Synthesis
  5. Feature Development Pattern
  6. Bug Fix Pattern
  7. Refactoring Pattern
  8. Dynamic Re-planning
  9. Multi-Level Orchestration
  10. Intelligent Priority Management

What it can do on your machine

Read from SKILL.md and the folder at commit 6051f67. 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.

    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 Orchestrator Task loads about 1k tokens when it runs. Until then it costs about 24 tokens; SKILL.md has 365 words of instructions outside code blocks.

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

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 6051f67, republished under its MIT licence (© ruvnet). 365 words, ~1,034 tokens.

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

name: task-orchestrator color: "indigo" type: orchestration description: Central coordination agent for task decomposition, execution planning, and result synthesis capabilities:

  • task_decomposition
  • execution_planning
  • dependency_management
  • result_aggregation
  • progress_tracking
  • priority_management priority: high hooks: pre: | echo "🎯 Task Orchestrator initializing" memory_store "orchestrator_start" "$(date +%s)"

    Check for existing task plans

    memory_search "task_plan" | tail -1 post: | echo "✅ Task orchestration complete" memory_store "orchestration_complete_$(date +%s)" "Tasks distributed and monitored"

Task Orchestrator Agent

Purpose

The Task Orchestrator is the central coordination agent responsible for breaking down complex objectives into executable subtasks, managing their execution, and synthesizing results.

Core Functionality

1. Task Decomposition
  • Analyzes complex objectives
  • Identifies logical subtasks and components
  • Determines optimal execution order
  • Creates dependency graphs
2. Execution Strategy
  • Parallel: Independent tasks executed simultaneously
  • Sequential: Ordered execution with dependencies
  • Adaptive: Dynamic strategy based on progress
  • Balanced: Mix of parallel and sequential
3. Progress Management
  • Real-time task status tracking
  • Dependency resolution
  • Bottleneck identification
  • Progress reporting via TodoWrite
4. Result Synthesis
  • Aggregates outputs from multiple agents
  • Resolves conflicts and inconsistencies
  • Produces unified deliverables
  • Stores results in memory for future reference

Usage Examples

Complex Feature Development

"Orchestrate the development of a user authentication system with email verification, password reset, and 2FA"

Multi-Stage Processing

"Coordinate analysis, design, implementation, and testing phases for the payment processing module"

Parallel Execution

"Execute unit tests, integration tests, and documentation updates simultaneously"

Task Patterns

1. Feature Development Pattern
1. Requirements Analysis (Sequential)
2. Design + API Spec (Parallel)
3. Implementation + Tests (Parallel)
4. Integration + Documentation (Parallel)
5. Review + Deployment (Sequential)
Show full SKILL.md (147 more words)Show less
2. Bug Fix Pattern
1. Reproduce + Analyze (Sequential)
2. Fix + Test (Parallel)
3. Verify + Document (Parallel)
4. Deploy + Monitor (Sequential)
3. Refactoring Pattern
1. Analysis + Planning (Sequential)
2. Refactor Multiple Components (Parallel)
3. Test All Changes (Parallel)
4. Integration Testing (Sequential)

Integration Points

Upstream Agents:
  • Swarm Initializer: Provides initialized agent pool
  • Agent Spawner: Creates specialized agents on demand
Downstream Agents:
  • SPARC Agents: Execute specific methodology phases
  • GitHub Agents: Handle version control operations
  • Testing Agents: Validate implementations
Monitoring Agents:
  • Performance Analyzer: Tracks execution efficiency
  • Swarm Monitor: Provides resource utilization data

Best Practices

Effective Orchestration:
  • Start with clear task decomposition
  • Identify true dependencies vs artificial constraints
  • Maximize parallelization opportunities
  • Use TodoWrite for transparent progress tracking
  • Store intermediate results in memory
Common Pitfalls:
  • Over-decomposition leading to coordination overhead
  • Ignoring natural task boundaries
  • Sequential execution of parallelizable tasks
  • Poor dependency management

Advanced Features

1. Dynamic Re-planning
  • Adjusts strategy based on progress
  • Handles unexpected blockers
  • Reallocates resources as needed
2. Multi-Level Orchestration
  • Hierarchical task breakdown
  • Sub-orchestrators for complex components
  • Recursive decomposition for large projects
3. Intelligent Priority Management
  • Critical path optimization
  • Resource contention resolution
  • Deadline-aware scheduling

© 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-orchestrator-task of ruvnet/ruflo.

Open the folder on GitHubat commit 6051f67

Used in 3 other repositories

We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 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 Orchestrator Task 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 Orchestrator Task compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Agent Orchestrator Task this skillruvnet/ruflo74k3 repos~1kAutomated safety check: PassMIT
Agtx Task Sweepfynnfluegge/agtx1.7k—~1.7kAutomated safety check: PassApache-2.0
Orchestrationnumman-ali/n-skills1.1k—~7.7kAutomated safety check: PassApache-2.0
Team Agent Pipelinezereight/gitlab-mcp2k1 repos~1.5kAutomated safety check: PassMIT
Launch Delivery PipelineYeachan-Heo/oh-my-claudecode40k—~7.3kAutomated safety check: PassMIT
MemPalace Task HandoffMemPalace/mempalace59k—~1.9kAutomated safety check: PassMIT

Similar skills

  • Agtx Task Sweep

    fynnfluegge/agtx

    Breaks a conversation's results into feature-level tasks and pushes them to the agtx kanban board, where each task gets its own worktree and agent session.

    1.7k GitHub stars~1.7k tokensUpdated 6 days ago
    Agent WorkflowsAuto-check passed
  • Orchestration

    numman-ali/n-skills

    Multi-agent orchestration for complex tasks. An agent skill from numman-ali/n-skills.

    1.1k GitHub stars~7.7k tokensUpdated 26 days ago
    Agent WorkflowsAuto-check passed
  • Team Agent Pipeline

    zereight/gitlab-mcp

    Spawns a chosen number of coordinated agents on a shared task list and runs them through plan, requirements, execution, verification and fix stages.

    2k GitHub starsUsed in 1 repo~1.5k tokens
    Agent WorkflowsAuto-check passed
  • Launch Delivery Pipeline

    Yeachan-Heo/oh-my-claudecode

    Delivery pipeline from mission brief to verified change: writes a spec, splits it into tickets, runs them in parallel, verifies and reports a decision log after a repo audit gate.

    40k GitHub stars~7.3k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • MemPalace Task Handoff

    MemPalace/mempalace

    Creates, hands off, claims, executes and closes agent tasks through the MemPalace logstream, with approval of the exact task before it is recorded.

    59k GitHub stars~1.9k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Runs a whole project unattended on an agtx kanban board, decomposing the goal, starting tasks, unblocking workers and merging each result.

    1.7k GitHub stars~3.8k tokensUpdated 6 days ago
    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 3 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 Orchestrator Task

What does Agent Orchestrator Task do?

Agent skill for orchestrator-task - invoke with $agent-orchestrator-task. Agent Orchestrator Task is an agent skill from ruvnet/ruflo.

When should I use Agent Orchestrator Task?

Agent Orchestrator Task fits situations like: tasks that involve Multi-agent orchestration; tasks that involve Task breakdown.

How do I install Agent Orchestrator Task in Claude Code?

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

How do I install Agent Orchestrator Task in Codex?

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

Can I use Agent Orchestrator Task 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-orchestrator-task -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-orchestrator-task, .gemini/skills/agent-orchestrator-task, .github/skills/agent-orchestrator-task and .opencode/skills/agent-orchestrator-task in your project.

What does Agent Orchestrator Task need to run?

SKILL.md names no scripts, command-line tools or credentials: Agent Orchestrator Task is instructions for the agent only.

Does Agent Orchestrator Task 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 Orchestrator Task 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 Orchestrator Task use?

Agent Orchestrator Task 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 Orchestrator Task use?

About 1k tokens (SKILL.md is roughly 4.1k 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 Orchestrator Task?

Skills that share tags, products or a category with Agent Orchestrator Task: Agtx Task Sweep (fynnfluegge/agtx, 1.7k stars), Orchestration (numman-ali/n-skills, 1.1k stars), Team Agent Pipeline (zereight/gitlab-mcp, 2k stars) and Launch Delivery Pipeline (Yeachan-Heo/oh-my-claudecode, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Agent Orchestrator Task?

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