Agent skill

Agent Team Orchestration

Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows.

MITAuto-check passedTesting & QA

Install Agent Team Orchestration

skills CLI

$ npx skills add aAAaqwq/AGI-Super-Team --skill agent-team-orchestration -a claude-code

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

GitHub CLI

$ gh skill install aAAaqwq/AGI-Super-Team agent-team-orchestration --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/aAAaqwq/AGI-Super-Team.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/agent-team-orchestration .claude/skills/agent-team-orchestration && 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/

Paste into Claude Code

Install the "agent-team-orchestration" agent skill from https://github.com/aAAaqwq/AGI-Super-Team/tree/main/skills/agent-team-orchestration into .claude/skills/agent-team-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-team-orchestration", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/aAAaqwq/AGI-Super-Team/tree/main/skills/agent-team-orchestration

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add aAAaqwq/AGI-Super-Team --skill agent-team-orchestration -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install aAAaqwq/AGI-Super-Team agent-team-orchestration --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/aAAaqwq/AGI-Super-Team.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/agent-team-orchestration .agents/skills/agent-team-orchestration && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "agent-team-orchestration" agent skill from https://github.com/aAAaqwq/AGI-Super-Team/tree/main/skills/agent-team-orchestration into .agents/skills/agent-team-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-team-orchestration", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add aAAaqwq/AGI-Super-Team --skill agent-team-orchestration -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install aAAaqwq/AGI-Super-Team agent-team-orchestration --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/aAAaqwq/AGI-Super-Team.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/agent-team-orchestration .cursor/skills/agent-team-orchestration && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "agent-team-orchestration" agent skill from https://github.com/aAAaqwq/AGI-Super-Team/tree/main/skills/agent-team-orchestration into .cursor/skills/agent-team-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-team-orchestration", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/aAAaqwq/AGI-Super-Team.git --path skills/agent-team-orchestration

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add aAAaqwq/AGI-Super-Team --skill agent-team-orchestration -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install aAAaqwq/AGI-Super-Team agent-team-orchestration --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/aAAaqwq/AGI-Super-Team.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/agent-team-orchestration .gemini/skills/agent-team-orchestration && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "agent-team-orchestration" agent skill from https://github.com/aAAaqwq/AGI-Super-Team/tree/main/skills/agent-team-orchestration into .gemini/skills/agent-team-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-team-orchestration", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install aAAaqwq/AGI-Super-Team agent-team-orchestration

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add aAAaqwq/AGI-Super-Team --skill agent-team-orchestration -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/aAAaqwq/AGI-Super-Team.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/agent-team-orchestration .github/skills/agent-team-orchestration && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "agent-team-orchestration" agent skill from https://github.com/aAAaqwq/AGI-Super-Team/tree/main/skills/agent-team-orchestration into .github/skills/agent-team-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-team-orchestration", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add aAAaqwq/AGI-Super-Team --skill agent-team-orchestration -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install aAAaqwq/AGI-Super-Team agent-team-orchestration --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/aAAaqwq/AGI-Super-Team.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/agent-team-orchestration .opencode/skills/agent-team-orchestration && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "agent-team-orchestration" agent skill from https://github.com/aAAaqwq/AGI-Super-Team/tree/main/skills/agent-team-orchestration into .opencode/skills/agent-team-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-team-orchestration", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: agent-team-orchestration
GitHub stars: 105
Used in: 3 other repos
Token cost: ~1.4k tokens
SKILL.md length: 581 words
Files: 7 (incl. references)
Skills in repo: 167
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows.

Works in 3 steps: Define Roles → Spawn a Task → Add a Reviewer
Setting up a team of 2+ agents with different specializations
SKILL.md covers Quick Start: Minimal 2-Agent…, Core Concepts, Reference Files and Common Pitfalls, plus 1 more section
Calls npm

What it does

Agent Team Orchestration is an agent skill from aAAaqwq/AGI-Super-Team. Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team of 2+ agents with different specializations, (2) Defining task routing and lifecycle (inbox → spec → build → review → done), (3) Creating handoff protocols between agents, (4) Establishing review and quality gates, (5) Managing async communication and artifact sharing between agents.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `.clawhub/origin.json`, `_meta.json` and `references/communication.md`).

It sits in Testing & QA, covering Multi-agent orchestration, Quality gates and Email management. The repository describes itself as: An installable, cross-framework AI organization: C-suite agents, expert subagents, curated skills, independent review, and one-command setup across 18 AI client/runtime adapters. The licence is MIT.

When your agent uses it

Setting up a team of 2+ agents with different specializations
Defining task routing and lifecycle (inbox → spec → build → review → done)
Creating handoff protocols between agents
Establishing review and quality gates

Example prompts

“/agent-team-orchestration”

Workflow steps

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

Define Roles
Spawn a Task
Add a Reviewer

What it can do on your machine

Read from SKILL.md and the folder at commit 331ecd3. 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
Shell commands in SKILL.md call:
- npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
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 Team Orchestration loads about 1.4k tokens when it runs, and up to ~5.2k if it reads all its reference files. Until then it costs about 112 tokens; SKILL.md has 581 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~112
When it runs · the whole SKILL.md, loaded when a task matches: ~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~5.2k

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 aAAaqwq/AGI-Super-Team at commit 331ecd3, republished under its MIT licence (© aAAaqwq). 581 words, ~1,414 tokens.

Download SKILL.mdSave it as .claude/skills/agent-team-orchestration/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.

name: agent-team-orchestration
description: Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team of 2+ agents with different specializations, (2) Defining task routing and lifecycle (inbox → spec → build → review → done), (3) Creating handoff protocols between agents, (4) Establishing review and quality gates, (5) Managing async communication and artifact sharing between agents.

Agent Team Orchestration

Production playbook for running multi-agent teams with clear roles, structured task flow, and quality gates.

Quick Start: Minimal 2-Agent Team

A builder and a reviewer. The simplest useful team.

1. Define Roles

Orchestrator (you) — Route tasks, track state, report results
Builder agent     — Execute work, produce artifacts

2. Spawn a Task

1. Create task record (file, DB, or task board)
2. Spawn builder with:
   - Task ID and description
   - Output path for artifacts
   - Handoff instructions (what to produce, where to put it)
3. On completion: review artifacts, mark done, report

3. Add a Reviewer

Builder produces artifact → Reviewer checks it → Orchestrator ships or returns

That's the core loop. Everything below scales this pattern.

Core Concepts

Roles

Every agent has one primary role. Overlap causes confusion.

Role	Purpose	Model guidance
Orchestrator	Route work, track state, make priority calls	High-reasoning model (handles judgment)
Builder	Produce artifacts — code, docs, configs	Can use cost-effective models for mechanical work
Reviewer	Verify quality, push back on gaps	High-reasoning model (catches what builders miss)
Ops	Cron jobs, standups, health checks, dispatching	Cheapest model that's reliable

→ Read references/team-setup.md when defining a new team or adding agents.

Task States

Every task moves through a defined lifecycle:

Inbox → Assigned → In Progress → Review → Done | Failed

Rules:

Orchestrator owns state transitions — don't rely on agents to update their own status
Every transition gets a comment (who, what, why)
Failed is a valid end state — capture why and move on

→ Read references/task-lifecycle.md when designing task flows or debugging stuck tasks.

Handoffs

When work passes between agents, the handoff message includes:

What was done — summary of changes/output
Where artifacts are — exact file paths
How to verify — test commands or acceptance criteria
Known issues — anything incomplete or risky
What's next — clear next action for the receiving agent

Bad handoff: "Done, check the files." Good handoff: "Built auth module at /shared/artifacts/auth/. Run npm test auth to verify. Known issue: rate limiting not implemented yet. Next: reviewer checks error handling edge cases."

Reviews

Cross-role reviews prevent quality drift:

Builders review specs — "Is this feasible? What's missing?"
Reviewers check builds — "Does this match the spec? Edge cases?"
Orchestrator reviews priorities — "Is this the right work right now?"

Skip the review step and quality degrades within 3-5 tasks. Every time.

→ Read references/communication.md when setting up agent communication channels. → Read references/patterns.md for proven multi-step workflows.

Reference Files

File	Read when...
team-setup.md	Defining agents, roles, models, workspaces
task-lifecycle.md	Designing task states, transitions, comments
communication.md	Setting up async/sync communication, artifact paths
patterns.md	Implementing specific workflows (spec→build→test, parallel research, escalation)

Show full SKILL.md (227 more words)Show less

Common Pitfalls

Spawning without clear artifact output paths

Agent produces great work, but you can't find it. Always specify the exact output path in the spawn prompt. Use a shared artifacts directory with predictable structure.

No review step = quality drift

"It's a small change, skip review." Do this three times and you have compounding errors. Every artifact gets at least one set of eyes that didn't produce it.

Agents not commenting on task progress

Silent agents create coordination blind spots. Require comments at: start, blocker, handoff, completion. If an agent goes silent, assume it's stuck.

Not verifying agent capabilities before assigning

Assigning browser-based testing to an agent without browser access. Assigning image work to a text-only model. Check capabilities before routing.

Orchestrator doing execution work

The orchestrator routes and tracks — it doesn't build. The moment you start "just quickly doing this one thing," you've lost oversight of the rest of the team.

When NOT to Use This Skill

Single-agent setups — Just follow standard AGENTS.md conventions. Team orchestration adds overhead that solo agents don't need.
One-off task delegation — Use sessions_spawn directly. This skill is for sustained workflows with multiple handoffs.
Simple question routing — If you're just forwarding a question to a specialist, that's a message, not a workflow.

This skill is for sustained team workflows — recurring collaboration patterns where agents depend on each other's output over multiple tasks.

Files

SKILL.md and 6 other files (references) in skills/agent-team-orchestration of aAAaqwq/AGI-Super-Team.

SKILL.md
.clawhub/origin.json
_meta.json
references/communication.md
references/patterns.md
references/task-lifecycle.md
references/team-setup.md

Open the folder on GitHubat commit 331ecd3

Used in 3 other repositories

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

Compare with similar skills

Agent Team Orchestration 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 Team Orchestration compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Agent Team Orchestration this skillaAAaqwq/AGI-Super-Team	105	3 repos	~1.4k	Automated safety check: Pass	MIT	today
Prompt Generatorcatlog22/Claude-Code-Workflow	2.1k	—	~4.7k	Automated safety check: Notes	MIT	3 mo ago
Multi Agent Task Orchestratorsickn33/agentic-awesome-skills	47k	2 repos	~1.5k	Automated safety check: Pass	MIT	today
Team Coordinationbybren-llc/safe-agentic-workflow	423	—	~1.9k	Automated safety check: Notes	MIT	2 mo ago
Cross-Platform Cloud Verificationwarpdotdev/warp	65k	1 repos	~2.6k	Automated safety check: Pass	AGPL-3.0	today
Long Horizon Promptingguanyang/open-agent-hub	977	1 repos	~6.4k	Automated safety check: Pass	MIT	yesterday

Similar skills

Prompt Generator
catlog22/Claude-Code-Workflow
Generate or convert Claude Code prompt files — command orchestrators, skill files, agent role definitions, or style conversion of existing files.
2.1k GitHub stars~4.7k tokensUpdated 3 mo ago
Testing & QAAuto-check: notes
Multi Agent Task Orchestrator
sickn33/agentic-awesome-skills
Route tasks to specialized AI agents with anti-duplication, quality gates, and 30-minute heartbeat monitoring
47k GitHub starsUsed in 2 repos~1.5k tokens
Testing & QAAuto-check passed
Team Coordination
bybren-llc/safe-agentic-workflow
Agent Teams orchestration patterns for multi-agent SAFe workflows.
423 GitHub stars~1.9k tokensUpdated 2 mo ago
Testing & QAAuto-check: notes
Cross-Platform Cloud Verification
warpdotdev/warp
Picks the smallest useful set of cloud OS and architecture runners to verify a change after local checks pass, then fans out child runs and aggregates the results.
65k GitHub starsUsed in 1 repo~2.6k tokens
Testing & QAAuto-check passed
Long Horizon Prompting
guanyang/open-agent-hub
This skill should be used when writing, enhancing, or evaluating the launch prompt for a long-running autonomous agent or a parallel multi-agent orchestration attacking a hard problem: pseudo-formal…
977 GitHub starsUsed in 1 repo~6.4k tokens
Agent WorkflowsAuto-check passed
Cao Supervisor Protocols
awslabs/cli-agent-orchestrator
Official
Supervisor-side orchestration patterns for assign, handoff, and idle inbox delivery in CAO
1.4k GitHub stars~1.2k tokensUpdated today
Agent WorkflowsAuto-check passed

Questions about Agent Team Orchestration

What does Agent Team Orchestration do?

Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Agent Team Orchestration is an agent skill from aAAaqwq/AGI-Super-Team. Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows.

When should I use Agent Team Orchestration?

Agent Team Orchestration fits situations like: setting up a team of 2+ agents with different specializations; defining task routing and lifecycle (inbox → spec → build → review → done); creating handoff protocols between agents; establishing review and quality gates.

How do I install Agent Team Orchestration in Claude Code?

Run `npx skills add aAAaqwq/AGI-Super-Team --skill agent-team-orchestration -a claude-code`. Or copy the skill folder (skills/agent-team-orchestration in aAAaqwq/AGI-Super-Team) into .claude/skills/agent-team-orchestration in your project. Claude Code loads it when a task matches its description.

How do I install Agent Team Orchestration in Codex?

Run `npx skills add aAAaqwq/AGI-Super-Team --skill agent-team-orchestration -a codex`. Or copy the skill folder (skills/agent-team-orchestration in aAAaqwq/AGI-Super-Team) into .agents/skills/agent-team-orchestration in your project. Codex loads it when a task matches its description.

Can I use Agent Team Orchestration 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 aAAaqwq/AGI-Super-Team --skill agent-team-orchestration -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-team-orchestration, .gemini/skills/agent-team-orchestration, .github/skills/agent-team-orchestration and .opencode/skills/agent-team-orchestration in your project.

What does Agent Team Orchestration need to run?

Going by SKILL.md and its folder, Agent Team Orchestration needs the command-line tools its instructions call (npm).

Does Agent Team Orchestration access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Agent Team Orchestration 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 Team Orchestration use?

Agent Team Orchestration 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 Team Orchestration use?

About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.8k tokens, read only when the agent opens those files.

What are the alternatives to Agent Team Orchestration?

Skills that share tags, products or a category with Agent Team Orchestration: Prompt Generator (catlog22/Claude-Code-Workflow, 2.1k stars), Multi Agent Task Orchestrator (sickn33/agentic-awesome-skills, 47k stars), Team Coordination (bybren-llc/safe-agentic-workflow, 423 stars) and Cross-Platform Cloud Verification (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Agent Team Orchestration?

aAAaqwq (a GitHub user) maintains it in aAAaqwq/AGI-Super-Team, which has 105 GitHub stars. The repository holds 167 skills in this directory. The repository was last updated on October 8, 2026.

Source: aAAaqwq/AGI-Super-Team on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Agent Team Orchestration

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Agent Team Orchestration

Quick Start: Minimal 2-Agent Team

1. Define Roles

2. Spawn a Task

3. Add a Reviewer

Core Concepts

Roles

Task States

Handoffs

Reviews

Reference Files

Common Pitfalls

Spawning without clear artifact output paths

No review step = quality drift

Agents not commenting on task progress

Not verifying agent capabilities before assigning

Orchestrator doing execution work

When NOT to Use This Skill

Files

Used in 3 other repositories

Compare with similar skills

Similar skills

More from aAAaqwq/AGI-Super-Team

Related

Questions about Agent Team Orchestration