Skip to main content
Agent skill

Team Builder

Interactive picker that discovers available agent personas via the claude agents command and agents/ markdown globs, groups them into domains, has the user select up to five, dispatches them in parallel on one task, and synthesizes agreements and conflicts into a unified report. Use when composing a team of agents, browsing available agent personas, or running several specialist agents in parallel.

Get started

Get the complete skill folder, including its scripts and reference files.

·

When to use this skill

Use Team Builder when an AI agent needs a reusable SKILL.md workflow for this job: Interactive picker that discovers available agent personas via the claude agents command and agents/ markdown globs, groups them into domains, has the user select up to five, dispatches them in parallel on one task, and synthesizes agreements and conflicts into a unified report. Use when composing a team of agents, browsing available agent personas, or running several specialist agents in parallel.

When not to use it

Skip Team Builder when the task is outside the productivity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/team-builder
# Save SKILL.md to ~/.claude/skills/team-builder/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/team-builder/SKILL.md. For a shared project, commit the folder at .claude/skills/team-builder/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Team Builder skill for this task: You have multiple agent personas (markdown files) and want to pick which ones to use for a task. Confirm any required inputs or files before making changes.

What supports this recommendation?

81/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
87/100
Practical detail
92/100
Source evidence
63/100
Source signals
72/100
Model compatibility evidence
  • claudeinferred

    The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Team Builder

Interactive menu for browsing and composing agent teams on demand. Works with flat or domain-subdirectory agent collections.

## When to Use

- You have multiple agent personas (markdown files) and want to pick which ones to use for a task - You want to compose an ad-hoc team from different domains (e.g., Security + SEO + Architecture) - You want to browse what agents are available before deciding

## Prerequisites

Agent files must be markdown files containing a persona prompt (identity, rules, workflow, deliverables). The first `# Heading` is used as the agent name and the first paragraph as the description.

Both flat and subdirectory layouts are supported:

**Subdirectory layout** — domain is inferred from the folder name:

``` agents/ ├── engineering/ │ ├── security-engineer.md │ └── software-architect.md ├── marketing/ │ └── seo-specialist.md └── sales/ └── discovery-coach.md ```

**Flat layout** — domain inferred from shared filename prefixes. A prefix counts as a domain when 2+ files share it. Files with unique prefixes go to "General". Note: the algorithm splits at the first `-`, so multi-word domains (e.g., `product-management`) should use the subdirectory layout instead:

``` agents/ ├── engineering-security-engineer.md ├── engineering-software-architect.md ├── marketing-seo-specialist.md ├── marketing-content-strategist.md ├── sales-discovery-coach.md └── sales-outbound-strategist.md ```

## Configuration

Agents are discovered via two methods, merged and deduplicated by agent name:

1. **`claude agents` command** (primary) — run `claude agents` to get all agents known to the CLI, including user agents, plugin agents (e.g. `ecc:architect`), and built-in agents. This automatically covers ECC marketplace installs without any path configuration. 2. **File glob** (fallback, for reading agent content) — agent markdown files are read from: - `./agents/**/*.md` + `./agents/*.md` — project-local agents - `~/.claude/agents/**/*.md` + `~/.claude/agents/*.md` — global user agents

Earlier sources take precedence when names collide: user agents > plugin agents > built-in agents. A custom path can be used instead if the user specifies one.

## How It Works

### Step 1: Discover Available Agents

Run `claude agents` to get the full agent list. Parse each line: - **Plugin agents** are prefixed with `plugin-name:` (e.g., `ecc:security-reviewer`). Use the part after `:` as the agent name and the plugin name as the domain. - **User agents** have no prefix. Read the corresponding markdown file from `~/.claude/agents/` or `./agents/` to extract the name and description. - **Built-in agents** (e.g., `Explore`, `Plan`) are skipped unless the user explicitly asks to include them.

For user agents loaded from markdown files: - **Subdirectory layout:** extract the domain from the parent folder name - **Flat layout:** collect all filename prefixes (text before the first `-`). A prefix qualifies as a domain only if it appears in 2 or more filenames (e.g., `engineering-security-engineer.md` and `engineering-software-architect.md` both start with `engineering` → Engineering domain). Files with unique prefixes (e.g., `code-reviewer.md`, `tdd-guide.md`) are grouped under "General" - Extract the agent name from the first `# Heading`. If no heading is found, derive the name from the filename (strip `.md`, replace hyphens with spaces, title-case) - Extract a one-line summary from the first paragraph after the heading

If no agents are found after running `claude agents` and probing file locations, inform the user: "No agents found. Run `claude agents` to verify your setup." Then stop.

### Step 2: Present Domain Menu

``` Available agent domains: 1. Engineering — Software Architect, Security Engineer 2. Marketing — SEO Specialist 3. Sales — Discovery Coach, Outbound Strategist

Pick domains or name specific agents (e.g., "1,3" or "security + seo"): ```

- Skip domains with zero agents (empty directories) - Show agent count per domain

### Step 3: Handle Selection

Accept flexible input: - Numbers: "1,3" selects all agents from Engineering and Sales - Names: "security + seo" fuzzy-matches against discovered agents - "all from engineering" selects every agent in that domain

If more than 5 agents are selected, list them alphabetically and ask the user to narrow down: "You selected N agents (max 5). Pick which to keep, or say 'first 5' to use the first five alphabetically."

Confirm selection: ``` Selected: Security Engineer + SEO Specialist What should they work on? (describe the task): ```

### Step 4: Spawn Agents in Parallel

1. Read each selected agent's markdown file 2. Prompt for the task description if not already provided 3. Spawn all agents in parallel using the Agent tool: - `subagent_type: "general-purpose"` - `prompt: "{agent file content}\n\nTask: {task description}"` - Each agent runs independently — no inter-agent communication needed 4. If an agent fails (error, timeout, or empty output), note the failure inline (e.g., "Security Engineer: failed — [reason]") and continue with results from agents that succeeded

### Step 5: Synthesize Results

Collect all outputs and present a unified report: - Results grouped by agent - Synthesis section highlighting: - Agreements across agents - Conflicts or tensions between recommendations - Recommended next steps

If only 1 agent was selected, skip synthesis and present the output directly.

## Rules

- **Dynamic discovery only.** Never hardcode agent lists. New files in the directory auto-appear in the menu. - **Max 5 agents per team.** More than 5 produces diminishing returns and excessive token usage. Enforce at selection time. - **Parallel dispatch.** All agents run simultaneously — use the Agent tool's parallel invocation pattern. - **Parallel Agent calls, not TeamCreate.** This skill uses parallel Agent tool calls for independent work. TeamCreate (a Claude Code tool for multi-agent dialogue) is only needed when agents must debate or respond to each other.

## Examples

``` User: team builder

Claude: Available agent domains: 1. Engineering (2) — Software Architect, Security Engineer 2. Marketing (1) — SEO Specialist 3. Sales (4) — Discovery Coach, Outbound Strategist, Proposal Strategist, Sales Engineer 4. Support (1) — Executive Summary

Pick domains or name specific agents:

User: security + seo

Claude: Selected: Security Engineer + SEO Specialist What should they work on?

User: Review my Next.js e-commerce site before launch

[Both agents spawn in parallel, each applying their specialty to the codebase]

Claude: ## Security Engineer Findings - [findings...]

## SEO Specialist Findings - [findings...]

## Synthesis Both agents agree on: [...] Tension: Security recommends CSP that blocks inline styles, SEO needs inline schema markup. Resolution: [...] Next steps: [...] ```

Intended uses

  • You have multiple agent personas (markdown files) and want to pick which ones to use for a task
  • You want to compose an ad-hoc team from different domains (e.g., Security + SEO + Architecture)
  • You want to browse what agents are available before deciding

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.