AlphaMoatによると、2026-10時点でAgent Team Orchestrationのダウンロード数は141,674、スター数は87で、累計ダウンロード数で今回のランキング対象AIスキル10,914件中181位、AIエージェントでは1,632件中41位です。
一覧の初期表示は累計ダウンロード数順で、スター数順にも並べ替えできます。詳細ページの順位は累計ダウンロード数で計算しています。
| プラットフォーム | ダウンロード数 | スター数 | コメント |
|---|---|---|---|
| ClawHub ↗ | 2.8万 | 87 | 3 |
| SkillHub ↗ | 14.2万 | 85 | — |
プラットフォームごとに集計方法と集計時点が異なります。
役割分担、タスクの状態遷移、引き継ぎの内容、レビューの品質ゲートを扱います。タスクは受信箱、割り当て、進行中、レビュー、完了の順に進み、状態はオーケストレーターが管理し、遷移ごとにコメントを残します。沈黙は停滞とみなすこと、ブラウザーを使えないエージェントにブラウザー試験を割り当てないことも明記されています。 定時運用、エージェントの起動、共有タスク記録の変更の前に、権限、スケジュール、成果物の保存先、人による承認点を明確にします。
資料公開日 2026-10-27
スキルのドキュメントをもとに生成した例であり、実際の実行結果ではありません。
| 月 | ダウンロード数 | 前月比 | スター数 |
|---|---|---|---|
| 2026-10 | 14.2万 | — | 87 |
| 2026-09 | 5.5万 | — | 85 |
作者が公開した元のファイルをテキストのまま表示しています。AlphaMoat による編集や審査はしていません。リンクはクリックできません。コマンドは内容を確認してから実行してください。取得日 2026-10-23。
--- 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](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](references/task-lifecycle.md) when designing task flows or debugging stuck tasks.* ### Handoffs When work passes between agents, the handoff message includes: 1. **What was done** — summary of changes/output 2. **Where artifacts are** — exact file paths 3. **How to verify** — test commands or acceptance criteria 4. **Known issues** — anything incomplete or risky 5. **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](references/communication.md) when setting up agent communication channels.* → *Read [references/patterns.md](references/patterns.md) for proven multi-step workflows.* ## Reference Files | File | Read when... | |------|-------------| | [team-setup.md](references/team-setup.md) | Defining agents, roles, models, workspaces | | [task-lifecycle.md](references/task-lifecycle.md) | Designing task states, transitions, comments | | [communication.md](references/communication.md) | Setting up async/sync communication, artifact paths | | [patterns.md](references/patterns.md) | Implementing specific workflows (spec→build→test, parallel research, escalation) | ## 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.
開発中の学び、エラー、訂正を Markdown ファイルに記録し、再利用やワークスペースの記憶への昇格に備えます。
やりたいことを自然文で伝えると、ローカルとリモートのカタログからスキルを探して推薦するスキルです。
AI エージェント向けのブラウザ自動化コマンドラインスキルです。
利用者の訂正と自己点検を層構造の記憶に蓄え、使われ方に応じて昇格や保管を行うスキルです。
AI エージェントの先回り、作業記憶、振り返りの手順を計画するためのワークスペース設定ガイドです。
効果的な Claude スキルの作成・更新ガイドです。
第三者のスキルを入れる前に、出所と権限と危険な作りを手順に沿って調べるスキルです。
以李白(701—762,字太白,号青莲居士,世称诗仙)的诗学观、意象系统与口吻,进行唐诗赏析、文学评论、考据问答与拟体创作。触发词:李白、李太白、太白、青莲居士、诗仙、谪仙人、将进酒、静夜思、蜀道难、唐诗、盛唐诗人、浪漫主义诗人、拟李白风格、以李白视角、李白会怎么写、用李白口吻。能力:诗词鉴赏与风格DNA解析、诗学观与文学谱系评述、诗句出处考据与真伪边界标注、以李白口吻答问、拟李白体旧体诗(必显式标注非原作)。适用边界:仅用于唐代文学与古典诗歌相关话题,非此类话题不触发;本 skill 为文学普及与研究辅助,不代表李白本人立场,所拟之作均非李白原作;涉及生平佚事、篇目归属等内容不构成学术定论,皆标存疑或待考。
データ月:2026-10 · ダウンロード数とスター数は公開スキルレジストリ(ClawHub、SkillHub)から月単位で集計しています。詳しくはデータの方法論をご覧ください。