New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

AI Team Orchestration

by github in github/awesome-copilot

Bootstrap and run a lightweight multi-agent development team.

OfficialMITAuto-check passedAgent Workflows

Install AI Team Orchestration

skills CLI
$ npx skills add github/awesome-copilot --skill ai-team-orchestration -a claude-code

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

GitHub CLI
$ gh skill install github/awesome-copilot ai-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/github/awesome-copilot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ai-team-orchestration .claude/skills/ai-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/

Facts

Skill name
ai-team-orchestration
GitHub stars
40k
Token cost
~992 tokens
SKILL.md length
440 words
Files
5 (incl. references)
Skills in repo
417
Repo updated
First seen
Licence
MIT

At a glance

Bootstrap and run a lightweight multi-agent development team.

  • Works in 5 steps: Read existing repository instructions… → Discover the actual stack, architecture,… → Create or update PROJECT_BRIEF.md only… → …
  • Adopting a project
  • SKILL.md covers Default Workflow, Start or Adopt a Project, Execute and Brainstorms, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

AI Team Orchestration is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Bootstrap and run a lightweight multi-agent development team. Use when starting or adopting a project, planning work, coordinating implementation and optional QA, brainstorming with distinct perspectives, or preserving context across sessions.

Its SKILL.md is about 990 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/anti-patterns.md`, `references/brainstorm-format.md` and `references/project-brief-template.md`).

It sits in Agent Workflows, covering Brainstorming, Project management and Multi-agent orchestration. The repository describes itself as: Community-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot. The licence is MIT.

When your agent uses it

  • Adopting a project
  • Coordinating implementation and optional QA
  • Brainstorming with distinct perspectives
  • Preserving context across sessions

Example prompts

  • “/ai-team-orchestration”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Read existing repository instructions and documentation.
  2. Discover the actual stack, architecture, commands, deployment model, and risks.
  3. Create or update PROJECT_BRIEF.md only when durable cross-session context is useful. Start from the project brief template and omit…
  4. For substantial work, create a concise plan from the sprint plan template.
  5. Use a separate branch or clone when parallel sessions could conflict, following the repository's own Git policy.

What it can do on your machine

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

AI Team Orchestration loads about 992 tokens when it runs, and up to ~3.7k if it reads all its reference files. Until then it costs about 66 tokens; SKILL.md has 440 words of instructions outside code blocks.

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

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 github/awesome-copilot at commit 727ff2e, republished under its MIT licence (© github). 440 words, ~992 tokens.

Download SKILL.mdSave it as .claude/skills/ai-team-orchestration/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
ai-team-orchestration
description
Bootstrap and run a lightweight multi-agent development team. Use when starting or adopting a project, planning work, coordinating implementation and optional QA, brainstorming with distinct perspectives, or preserving context across sessions.

AI Team Orchestration

Use three stable agents:

AgentPurpose
@ai-team-producerClarify scope, plan proportionately, coordinate, and merge
@ai-team-devImplement, test, self-review, and prepare the pull request
@ai-team-qaIndependently test behavior when dedicated QA is useful

Nova, Sage, and Milo are perspectives inside the Dev agent, not mandatory project layers.

Default Workflow

Plan -> Implement -> Test -> optional review or QA -> Merge -> update project state

Keep the workflow proportional:

  • Skip formal planning for small, obvious changes.
  • Use a short plan for multi-step or cross-cutting work.
  • Add independent review or QA when risk, uncertainty, or repository policy justifies it.
  • Let branch protection, required checks, permissions, and merge queues enforce repository merge policy.

Start or Adopt a Project

  1. Read existing repository instructions and documentation.
  2. Discover the actual stack, architecture, commands, deployment model, and risks.
  3. Create or update PROJECT_BRIEF.md only when durable cross-session context is useful. Start from the project brief template and omit irrelevant sections.
  4. For substantial work, create a concise plan from the sprint plan template.
  5. Use a separate branch or clone when parallel sessions could conflict, following the repository's own Git policy.

Execute

Producer
  • Define the outcome, constraints, acceptance criteria, and explicit exclusions.
  • Choose review and QA based on risk rather than ceremony.
  • Keep durable project state concise and current.
Dev
  • Follow repository conventions and implement the smallest complete solution.
  • Run relevant checks and inspect the final diff.
  • Open or update the pull request with summary, verification, and limitations.
QA
  • Use only when dedicated behavioral verification adds value.
  • Test the requested change and important regressions.
  • Report reproducible findings and verify fixes.
Show full SKILL.md (177 more words)Show less

Brainstorms

Use the brainstorm format for product or architecture decisions that benefit from competing perspectives. For ordinary implementation choices, let Dev decide using repository conventions.

Context Recovery

Before ending a long or interrupted session:

  1. Update the active plan or progress note if one exists.
  2. Record material decisions, blockers, and the next action in repository context.
  3. Use a cold-start prompt such as:
text
Read the repository instructions, then read whichever sources exist for this
work: the active issue or request, PROJECT_BRIEF.md, and the active plan or
progress note.
Continue from the recorded next action.

Tool and Model Inheritance

The bundled agents intentionally omit tools and model frontmatter:

  • available built-in, MCP, and extension tools remain usable;
  • developers keep control of model selection;
  • role boundaries are defined by instructions and normal trust, permission, authentication, and approval controls.

If the environment exposes too many tools, deselect irrelevant tools or MCP servers, or use VS Code virtual-tool management. Do not add a machine-specific plugin allowlist.

Principles

  • Prefer working software and clear handoffs over process artifacts.
  • Follow repository policy instead of embedding universal Git commands.
  • Preserve unknown work and ask before destructive or privileged actions.
  • Keep bugs and important decisions in durable project systems, not only chat.
  • See anti-patterns for concise lessons.

© github, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in skills/ai-team-orchestration of github/awesome-copilot.

  • SKILL.md
  • references/anti-patterns.md
  • references/brainstorm-format.md
  • references/project-brief-template.md
  • references/sprint-plan-template.md

Open the folder on GitHubat commit 727ff2e

Compare with similar skills

AI 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.

AI Team Orchestration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
AI Team Orchestration this skillgithub/awesome-copilot40k—~992Automated safety check: PassMIT
Team Taskswin4r/team-tasks447—~2.9kAutomated safety check: PassNone
Codex Issue Coordinatorowainlewis/blueprint412—~2.6kAutomated safety check: PassMIT
PadPerpetualSoftware/pad185—~10kAutomated safety check: NotesApache-2.0
Design Orchestrationaiskillstore/marketplace4305 repos~952Automated safety check: PassNone
Multi Agent Brainstormingaiskillstore/marketplace4305 repos~1.4kAutomated safety check: PassNone

Similar skills

  • Team Tasks

    win4r/team-tasks

    Coordinate multi-agent development pipelines using shared JSON task files.

    447 GitHub stars~2.9k tokensUpdated 8 mo ago
    Agent WorkflowsAuto-check passed

  • Codex Issue Coordinator

    owainlewis/blueprint

    Lets one Codex thread run a batch of GitHub issues through separate worker threads, each with its own worktree, branch, tested pull request and gated merge.

    412 GitHub stars~2.6k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • Pad

    PerpetualSoftware/pad

    Talk to your project. An agent skill from PerpetualSoftware/pad.

    185 GitHub stars~10k tokensUpdated today
    Agent WorkflowsAuto-check: notes

  • Design Orchestration

    aiskillstore/marketplace

    Orchestrates design workflows by routing work through brainstorming, multi-agent review, and execution readiness in the correct order.

    430 GitHub starsUsed in 5 repos~952 tokens
    Agent WorkflowsAuto-check passed

  • Multi Agent Brainstorming

    aiskillstore/marketplace

    Simulate a structured peer-review process using multiple specialized agents to validate designs, surface hidden assumptions, and identify failure modes before implementation.

    430 GitHub starsUsed in 5 repos~1.4k tokens
    Agent WorkflowsAuto-check passed

  • Pm Brainstorm

    bex-co/beancount-io

    Propose milestones and tasks for the repository's public .pm adoption board — decompose a topic through the TPM adoption lens, size and gate the work, and emit a text-only proposal for /pm to…

    294 GitHub stars~1.6k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from github/awesome-copilot

All 417 skills in this repo

  • Acquire Codebase Knowledge

    github/awesome-copilot

    Official

    Maps an unfamiliar codebase into seven evidence-backed documents in docs/codebase/, using a scan script and templates, for onboarding or architecture write-ups.

    40k GitHub starsUsed in 1 repo~2.3k tokens
    Auto-check passed

  • Azure Architecture Autopilot

    github/awesome-copilot

    Official

    Designs Azure infrastructure from a natural-language description, or diagrams an existing resource group, then refines the design through conversation and deploys it with Bicep.

    40k GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed

  • Draw.io Diagram Generator

    github/awesome-copilot

    Official

    Generates, edits and validates draw.io files with correct mxGraph XML, covering flowcharts, architecture, sequence, ER and UML class diagrams.

    40k GitHub starsUsed in 1 repo~4.9k tokens
    Auto-check passed

  • Credit Risk Data Cleaning

    github/awesome-copilot

    Official

    Cleans raw credit data and screens variables before loan modeling, dropping unstable, noisy or redundant features and writing an Excel report of every step.

    40k GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed

  • Daily Focus Board

    github/awesome-copilot

    Official

    Builds a warm, browser-based daily focus board the user updates by talking to their agent, with Eisenhower priorities, a brain-dump box and kind not-today carryover.

    40k GitHub stars~3k tokensUpdated today
    Auto-check passed

  • Python Pypi Package Builder

    github/awesome-copilot

    Official

    End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI.

    40k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Categories

Questions about AI Team Orchestration

What does AI Team Orchestration do?

Bootstrap and run a lightweight multi-agent development team. AI Team Orchestration is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Bootstrap and run a lightweight multi-agent development team.

When should I use AI Team Orchestration?

AI Team Orchestration fits situations like: adopting a project; coordinating implementation and optional QA; brainstorming with distinct perspectives; preserving context across sessions.

How do I install AI Team Orchestration in Claude Code?

Run `npx skills add github/awesome-copilot --skill ai-team-orchestration -a claude-code`. Or copy the skill folder (skills/ai-team-orchestration in github/awesome-copilot) into .claude/skills/ai-team-orchestration in your project. Claude Code loads it when a task matches its description.

How do I install AI Team Orchestration in Codex?

Run `npx skills add github/awesome-copilot --skill ai-team-orchestration -a codex`. Or copy the skill folder (skills/ai-team-orchestration in github/awesome-copilot) into .agents/skills/ai-team-orchestration in your project. Codex loads it when a task matches its description.

Can I use AI 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 github/awesome-copilot --skill ai-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/ai-team-orchestration, .gemini/skills/ai-team-orchestration, .github/skills/ai-team-orchestration and .opencode/skills/ai-team-orchestration in your project.

What does AI Team Orchestration need to run?

SKILL.md names no scripts, command-line tools or credentials: AI Team Orchestration is instructions for the agent only.

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

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

About 992 tokens (SKILL.md is roughly 4k 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 2.7k tokens, read only when the agent opens those files.

What are the alternatives to AI Team Orchestration?

Skills that share tags, products or a category with AI Team Orchestration: Team Tasks (win4r/team-tasks, 447 stars), Codex Issue Coordinator (owainlewis/blueprint, 412 stars), Pad (PerpetualSoftware/pad, 185 stars) and Design Orchestration (aiskillstore/marketplace, 430 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains AI Team Orchestration?

github (a GitHub organization, an official publisher) maintains it in github/awesome-copilot, which has 39,748 GitHub stars. The repository holds 417 skills in this directory. The repository was last updated on October 7, 2026.

Source: github/awesome-copilot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.