Individual skill

agent-orchestration

Orchestrate agents at runtime — task routing, scheduling, parallel execution, result aggregation, and supervision dashboards. Use when running agents as a managed fleet rather than one-off calls.

skills/agent-orchestration/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
54
Repository last updated
Oct 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Agent Orchestration

Orchestration is the runtime layer: taking agents as workers and running them as a system — 
routing tasks, scheduling execution, handling parallelism, aggregating results, and supervising the 
whole fleet. Architecture designs the team; orchestration runs it.

## Overview

An orchestrator owns the task lifecycle: intake (validate and normalize requests), planning 
(decompose into subtasks), dispatch (assign to agents with briefs), supervision (track progress, 
handle stalls), aggregation (combine results), and delivery. Underneath: queues, worker pools, 
retries, timeouts, and rate limits. The orchestrator is also the policy enforcement point — 
budgets, permissions, and escalation all live here.
Back to top