Analyze tasks and dynamically assemble expert agent teams using Claude Code's TeamCreate API.

MITAuto-check: notesAgent Workflows

Install Team Assemble

skills CLI
$ npx skills add team-attention/plugins-for-claude-natives --skill team-assemble -a claude-code

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

GitHub CLI
$ gh skill install team-attention/plugins-for-claude-natives team-assemble --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/team-attention/plugins-for-claude-natives.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/team-assemble/skills/team-assemble .claude/skills/team-assemble && 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
team-assemble
GitHub stars
827
Token cost
~2.1k tokens
SKILL.md length
685 words
Files
5 (incl. references)
Skills in repo
16
Repo updated
First seen
Licence
MIT

At a glance

Analyze tasks and dynamically assemble expert agent teams using Claude Code's TeamCreate API.

  • Works in 6 steps: Task Analysis → Codebase Scouts (Parallel) → Integrate & Confirm Team → …
  • Agent Workflows work in your project
  • SKILL.md covers Prerequisites, When to Use, Core Principles and Workflow, plus 8 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Team Assemble is an agent skill from team-attention/plugins-for-claude-natives. Analyze tasks and dynamically assemble expert agent teams using Claude Code's TeamCreate API. Scouts your codebase, designs optimal agents, and executes with validation.

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/agents.md`, `references/enable-agent-teams.md` and `references/examples.md`).

It sits in Agent Workflows. The repository describes itself as: Claude Code plugins for power users. The licence is MIT.

When your agent uses it

  • Agent Workflows work in your project

Example prompts

  • “/team-assemble”

Requirements

  • Pre-approved tools (allowed-tools): Agent, Bash, Read, Write, Edit, Glob, Grep, AskUserQuestion, TaskCreate, TaskUpdate, TaskList, TaskGet, TeamCreate, TeamDelete, SendMessage

Workflow steps

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

  1. Task Analysis
  2. Codebase Scouts (Parallel)
  3. Integrate & Confirm Team
  4. Execution
  5. Validation
  6. Complete & Cleanup

What it can do on your machine

Read from SKILL.md and the folder at commit fd9c207. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Agent
    • Bash
    • Read
    • Write
    • Edit
    • Glob
    • Grep
    • AskUserQuestion
    • TaskCreate
    • TaskUpdate

    …and 5 more on the same allowed-tools line.

    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

Team Assemble loads about 2.1k tokens when it runs, and up to ~6.6k if it reads all its reference files. Until then it costs about 46 tokens; SKILL.md has 685 words of instructions outside code blocks.

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

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Agent, Bash, Read, Write, Edit, Glob, Grep, AskUserQuestion, TaskCreate, TaskUpdate, TaskList, TaskG

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 team-attention/plugins-for-claude-natives at commit fd9c207, republished under its MIT licence (© team-attention). 685 words, ~2,068 tokens.

Download SKILL.mdSave it as .claude/skills/team-assemble/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
team-assemble
description
Analyze tasks and dynamically assemble expert agent teams using Claude Code's TeamCreate API. Scouts your codebase, designs optimal agents, and executes with validation.
allowed-tools
Agent, Bash, Read, Write, Edit, Glob, Grep, AskUserQuestion, TaskCreate, TaskUpdate, TaskList, TaskGet, TeamCreate, TeamDelete, SendMessage
version
1.0.0

Team Assemble

Analyze a task, dynamically design the right expert agents, and orchestrate them as a team using Claude Code's agent teams feature.

Prerequisites

Agent teams must be enabled. See references/enable-agent-teams.md for setup instructions.

When to Use

  • Complex tasks that decompose into 2+ independent subtasks
  • Work where role separation is clear (e.g., research + implementation + validation)
  • Tasks that benefit from parallel execution

Do NOT use for: single-file edits, simple questions, purely sequential work


Core Principles

  • Model 3-tier — choose by role purpose (details: references/agents.md)
    • opus — strategy/judgment (scouts, complex execution)
    • sonnet — standard execution/validation (worker, qa, support)
    • haiku — exploration/writing (researcher, editor)
  • No fixed catalog — agents are designed dynamically per task
  • Example bank — references/agents.md provides reference examples (not mandatory)

Workflow

Phase 1 → Phase 2 → Phase 3 → Phase 4 → Phase 5 → Phase 6
Task       Codebase   Integrate  Execute   Validate   Complete
Analysis   Scouts     & Confirm                       & Cleanup
                                           ↕ FAIL → support fix (max 3x)

Phase 1: Task Analysis

Analyze the user's request and identify relevant areas of the codebase:

  1. Examine project structure, CLAUDE.md files, and README files
  2. Identify which parts of the codebase are relevant to the task
  3. Determine if codebase scouting (Phase 2) would help, or if the task is straightforward enough to skip to Phase 3

Get user approval via AskUserQuestion:

I've analyzed your task and identified the following areas of interest:

- [x] src/auth/ — Authentication module (needs refactoring)
- [x] tests/auth/ — Corresponding tests
- [ ] src/api/ — Not directly affected

I'll scout these areas to design an optimal team.

Options: "Looks good, proceed" / "I'd like to adjust the scope"

For straightforward tasks that don't need codebase exploration, skip Phase 2 and go directly to Phase 3 — design the team yourself using references/agents.md as a guide.


Phase 2: Codebase Scouts (Parallel)

Launch scout agents in parallel to explore relevant areas of the codebase.

Scout Configuration
  • Model: opus
  • subagent_type: general-purpose (constrained to read-only via prompt)
  • Parallel: launch multiple scouts simultaneously when exploring different areas
Scout Mission

Each scout reads the relevant codebase area and proposes agents for the task:

  1. Read key files (CLAUDE.md, README.md, source code, configs)
  2. Analyze the intersection between the task and the codebase area
  3. Propose agents needed (name, role, tasks, reference files)
  4. Reference references/agents.md for examples, but freely design new agents

Prompt template: references/prompt-templates.md § Codebase Scout

Scout Output Format
## Scout Report: {area}

### Current State
- {file structure summary}
- {relevance to the task}

### Proposed Agents
| Agent | Role | Tasks | Reference Files |
|-------|------|-------|-----------------|
| {name} | {role} | {task} | {files} |

### Notes
- {area-specific constraints or patterns to follow}

Phase 3: Integrate & Confirm Team

Merge scout reports into a final team composition:

  1. Deduplicate — merge similar agent proposals from different scouts
  2. Gap analysis — check for missing roles
  3. Add qa + support — validation/fix agents are always included
  4. Dependency graph — design execution order between agents
  5. Define acceptance criteria — measurable criteria for Phase 5 validation
Team Proposal

Get final approval via AskUserQuestion:

Proposed team: {team-name}

| # | Agent | Role | Tasks | Dependencies |
|---|-------|------|-------|--------------|
| 1 | architect | System design | Design new auth flow | - |
| 2 | implementer | Code changes | Implement the design | #1 |
| 3 | test-writer | Test coverage | Write tests for changes | #2 |
| 4 | qa | Validation | PASS/FAIL against acceptance criteria | #2, #3 |

Acceptance criteria:
- [ ] AC-1: {measurable criterion}
- [ ] AC-2: {measurable criterion}

Options: "Looks good, execute" / "I'd like to adjust roles"

If the user selects "adjust roles", ask what specifically to change. After 2+ revision requests, switch to free-text input.


Phase 4: Execution

Show full SKILL.md (279 more words)Show less
Create Team & Distribute Tasks
TeamCreate(team_name: "{keyword}-team", description: "Task description")

team_name convention: core keyword + -team

Create TaskCreate entries for each agent, then set dependencies with TaskUpdate.

Launch Teammates
  • Model: apply 3-tier based on role (references/agents.md)
  • subagent_type: "general-purpose"
  • mode: "bypassPermissions"
  • Parallel: launch agents without blockedBy dependencies in a single message
  • Sequential: inject preceding agent results into the next agent's prompt
Teammate Prompt Requirements
  1. Context — project background and how this task fits the whole
  2. Specific goal — exactly what to achieve
  3. Reference files — file paths identified by scouts
  4. Constraints — what NOT to do, scope limits
  5. Output format — expected deliverable format
  6. Team info — team_name, task ID

Detailed prompt structure: references/prompt-templates.md


Phase 5: Validation

qa (sonnet) evaluates each acceptance criterion from Phase 3.

Validation Process
Agent(name: "qa", model: "sonnet", prompt: """
## Acceptance Criteria
- [ ] AC-1: {criterion}

## Validation Target
{Phase 4 execution results}

Evaluate each criterion with evidence-based PASS/FAIL judgment.
No PASS without evidence.

## Output Format
| # | Criterion | Verdict | Evidence |
Overall: PASS / FAIL
Include fix suggestions for any FAIL items.
""")
FAIL Handling

support (sonnet) fixes only FAIL items → qa re-validates:

  • Max 3 rounds of verify/fix loop
  • If the same error repeats 3 times, stop immediately
  • After 3 rounds, halt the pipeline and report to user:
## Validation Failed — Manual Intervention Needed

### Repeated Failures
- AC-{N}: {criterion} — {failure reason}

### Attempted Fixes
1. {attempt 1}  2. {attempt 2}  3. {attempt 3}

### Recommended Action
{what needs to be done manually}

Phase 6: Complete & Cleanup

Result Report
## Team Results: {team-name}

### Acceptance Criteria
- [x] AC-1: {criterion} — PASS

### Per-Agent Results
- {agent}: {result summary}

### Deliverables
- {file paths or outputs}

### Validation History
- Validated {N} times, {M} fixes applied
Team Cleanup
SendMessage(type: "shutdown_request", recipient: "{name}", content: "Work complete")
TeamDelete()

Common Mistakes

MistakeCorrect Approach
Creating team without user approvalGet AskUserQuestion approval in Phase 1 + Phase 3
Executing without acceptance criteriaAlways define criteria in Phase 3
Running scouts for simple tasksSkip Phase 2 for straightforward work
Skipping validationAlways run Phase 5 after execution
Ignoring model tiersUse opus/sonnet/haiku based on role purpose
Only picking from fixed catalogScouts design freely; examples are reference only
Forgetting TeamDeleteAlways shutdown_request → TeamDelete
Infinite FAIL loopMax 3 verify/fix rounds, then report to user

Additional Resources

  • references/agents.md — Agent example bank with model tier guide
  • references/prompt-templates.md — Scout + execution + QA prompt templates
  • references/examples.md — Worked examples: feature dev, refactoring, research
  • references/enable-agent-teams.md — How to enable agent teams in Claude Code

© team-attention, 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 plugins/team-assemble/skills/team-assemble of team-attention/plugins-for-claude-natives.

  • SKILL.md
  • references/agents.md
  • references/enable-agent-teams.md
  • references/examples.md
  • references/prompt-templates.md

Open the folder on GitHubat commit fd9c207

Compare with similar skills

Team Assemble 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.

Team Assemble compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Team Assemble this skillteam-attention/plugins-for-claude-natives827—~2.1kAutomated safety check: NotesMIT
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k10 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k35 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers297k2 repos~5.1kAutomated safety check: PassMIT
Skill CreatorAzure/azqr79589 repos~8.2kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 10 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes
  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 35 repos~1.4k tokens
    Agent WorkflowsAuto-check passed
  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    297k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed
  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    795 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 7 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

More from team-attention/plugins-for-claude-natives

All 16 skills in this repo
  • Gmail

    team-attention/plugins-for-claude-natives

    This skill should be used when the user asks to "check email", "read emails", "send email", "reply to email", "search inbox", or manages Gmail.

    827 GitHub stars~967 tokensUpdated 5 mo ago
    Auto-check passed
  • History Insight

    team-attention/plugins-for-claude-natives

    This skill should be used when user wants to access, capture, or reference Claude Code session history.

    827 GitHub stars~834 tokensUpdated 5 mo ago
    Auto-check passed
  • Session Analyzer

    team-attention/plugins-for-claude-natives

    This skill should be used when the user asks to "analyze session", "세션 분석", "evaluate skill execution", "스킬 실행 검증", "check session logs", "로그 분석", provides a session ID with a skill path, or wants…

    827 GitHub stars~1.8k tokensUpdated 5 mo ago
    Auto-check passed
  • Youtube Digest

    team-attention/plugins-for-claude-natives

    This skill should be used when the user asks to "유튜브 정리", "영상 요약", "transcript 번역", "YouTube digest", "영상 퀴즈", or provides a YouTube URL for analysis.

    827 GitHub stars~557 tokensUpdated 5 mo ago
    Auto-check passed
  • Tech Decision

    team-attention/plugins-for-claude-natives

    This skill should be used when the user asks to "기술 의사결정", "뭐 쓸지 고민", "A vs B", "비교 분석", "라이브러리 선택", "아키텍처 결정", "어떤 걸 써야 할지", "트레이드오프", "기술 선택", "구현 방식 고민", or needs deep analysis for technical…

    827 GitHub starsUsed in 2 repos~1.2k tokens
    Auto-check passed
  • Fetch Tweet

    team-attention/plugins-for-claude-natives

    This skill should be used when the user asks to "트윗 가져와", "트윗 번역", "X 게시글 읽어줘", "tweet fetch", "트윗 내용", "트윗 원문", or provides an X/Twitter URL (x.com, twitter.com) and wants to read, translate, or…

    827 GitHub stars~518 tokensUpdated 5 mo ago
    Auto-check passed

Categories

Questions about Team Assemble

What does Team Assemble do?

Analyze tasks and dynamically assemble expert agent teams using Claude Code's TeamCreate API. Team Assemble is an agent skill from team-attention/plugins-for-claude-natives. Analyze tasks and dynamically assemble expert agent teams using Claude Code's TeamCreate API.

When should I use Team Assemble?

Team Assemble fits situations like: agent Workflows work in your project.

How do I install Team Assemble in Claude Code?

Run `npx skills add team-attention/plugins-for-claude-natives --skill team-assemble -a claude-code`. Or copy the skill folder (plugins/team-assemble/skills/team-assemble in team-attention/plugins-for-claude-natives) into .claude/skills/team-assemble in your project. Claude Code loads it when a task matches its description.

How do I install Team Assemble in Codex?

Run `npx skills add team-attention/plugins-for-claude-natives --skill team-assemble -a codex`. Or copy the skill folder (plugins/team-assemble/skills/team-assemble in team-attention/plugins-for-claude-natives) into .agents/skills/team-assemble in your project. Codex loads it when a task matches its description.

Can I use Team Assemble 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 team-attention/plugins-for-claude-natives --skill team-assemble -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/team-assemble, .gemini/skills/team-assemble, .github/skills/team-assemble and .opencode/skills/team-assemble in your project.

What does Team Assemble need to run?

SKILL.md names no scripts, command-line tools or credentials: Team Assemble is instructions for the agent only. Its frontmatter pre-approves these tools: Agent, Bash, Read, Write, Edit, Glob, Grep, AskUserQuestion, TaskCreate, TaskUpdate, TaskList, TaskGet, TeamCreate, TeamDelete, SendMessage.

Does Team Assemble 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 Team Assemble safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Team Assemble use?

Team Assemble 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 Team Assemble use?

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

What are the alternatives to Team Assemble?

Skills that share tags, products or a category with Team Assemble: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Team Assemble?

team-attention (a GitHub organization) maintains it in team-attention/plugins-for-claude-natives, which has 827 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on April 20, 2026.

Source: team-attention/plugins-for-claude-natives on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.