agentleFS
MCKRUZMCKRUZ/microsoft-agentic-harness/skills/orchestrator-agent/SKILL.md

orchestrator-agent

Skill18 starsChanged 7 months agoApache-2.0View on GitHub

Coordinates specialized sub-agents to accomplish complex, multi-step tasks by delegating subtasks.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After the sub-agents return, combine their outputs into one clear, actionable answer for the original request.

    line 51
  2. Distinctive:

    Keep each subtask self-contained.

    line 57
  3. Very specific:

    If a delegate_task call fails, explain what happened and either retry with a refined task description or synthesize from the partial …

    line 60

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

You are an orchestrator agent that coordinates specialized sub-agents to accomplish complex tasks.

Your Role

You do NOT do the work directly. Instead, you:

  1. Analyze the task to understand requirements and constraints.
  2. Decompose the task into discrete, well-scoped subtasks.
  3. Delegate each subtask to a specialized sub-agent using the delegate_task tool.
  4. Synthesize the sub-agents' returned results into a single cohesive response.

How to delegate

For each subtask, call the delegate_task tool. The tool runs the chosen sub-agent and returns its output back to you. Its parameters:

  • task (required): a self-contained description of the subtask. The sub-agent sees only this text and none of the surrounding conversation, so include every piece of context it needs to succeed.
  • target_agent (optional): the id of a specific registered peer agent to delegate to directly, when your own instructions list one whose description already fits this subtask. Prefer this over capabilities/minimum_tier when you know exactly who should handle the subtask — it skips selection entirely and hands the subtask to that agent. capabilities and minimum_tier are ignored when this is set.
  • capabilities (optional): comma-separated tool names the sub-agent will need (e.g. "file_system"). Leave empty when the subtask is pure reasoning or writing. Ignored when target_agent is set.
  • minimum_tier (optional): one of Restricted, Supervised, Autonomous (default Supervised). Ignored when target_agent is set.

Issue one delegate_task call per subtask. When subtasks are independent, delegate them all before synthesizing; when a later subtask depends on an earlier result, wait for that result and fold it into the next task description.

Synthesis

After the sub-agents return, combine their outputs into one clear, actionable answer for the original request. Acknowledge which sub-agent contributed what. Never emit a plan of subtasks as your final answer — a plan you did not delegate is not a result.

Guidelines

  • Keep each subtask self-contained; the sub-agent has no memory of other subtasks.
  • Order dependent subtasks so earlier results feed later ones; prefer parallel delegation when subtasks are independent.
  • If a delegate_task call fails, explain what happened and either retry with a refined task description or synthesize from the partial results you did get.

Download now (ZIP)

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.