Team Builder
affaan-m/ECC
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…
Interactive agent picker for composing and dispatching parallel teams
MITAuto-check passed
Install Team Builder
$ npx skills add loulanyue/awesome-claude-notes --skill team-builder -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install loulanyue/awesome-claude-notes team-builder --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/loulanyue/awesome-claude-notes.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/team-builder .claude/skills/team-builder && rm -rf skills-srcUse ~/.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/
Install the "team-builder" agent skill from https://github.com/loulanyue/awesome-claude-notes/tree/main/skills/team-builder into .claude/skills/team-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-builder", 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 install https://github.com/loulanyue/awesome-claude-notes/tree/main/skills/team-builderType 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.
$ npx skills add loulanyue/awesome-claude-notes --skill team-builder -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install loulanyue/awesome-claude-notes team-builder --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/loulanyue/awesome-claude-notes.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/team-builder .agents/skills/team-builder && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "team-builder" agent skill from https://github.com/loulanyue/awesome-claude-notes/tree/main/skills/team-builder into .agents/skills/team-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-builder", 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.
$ npx skills add loulanyue/awesome-claude-notes --skill team-builder -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install loulanyue/awesome-claude-notes team-builder --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/loulanyue/awesome-claude-notes.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/team-builder .cursor/skills/team-builder && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "team-builder" agent skill from https://github.com/loulanyue/awesome-claude-notes/tree/main/skills/team-builder into .cursor/skills/team-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-builder", 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 https://github.com/loulanyue/awesome-claude-notes.git --path skills/team-builder--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add loulanyue/awesome-claude-notes --skill team-builder -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install loulanyue/awesome-claude-notes team-builder --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/loulanyue/awesome-claude-notes.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/team-builder .gemini/skills/team-builder && rm -rf skills-srcUse ~/.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/
Install the "team-builder" agent skill from https://github.com/loulanyue/awesome-claude-notes/tree/main/skills/team-builder into .gemini/skills/team-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-builder", 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.
$ gh skill install loulanyue/awesome-claude-notes team-builderInstalls 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).
$ npx skills add loulanyue/awesome-claude-notes --skill team-builder -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/loulanyue/awesome-claude-notes.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/team-builder .github/skills/team-builder && rm -rf skills-srcUse ~/.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/
Install the "team-builder" agent skill from https://github.com/loulanyue/awesome-claude-notes/tree/main/skills/team-builder into .github/skills/team-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-builder", 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.
$ npx skills add loulanyue/awesome-claude-notes --skill team-builder -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install loulanyue/awesome-claude-notes team-builder --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/loulanyue/awesome-claude-notes.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/team-builder .opencode/skills/team-builder && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "team-builder" agent skill from https://github.com/loulanyue/awesome-claude-notes/tree/main/skills/team-builder into .opencode/skills/team-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-builder", 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
team-builder- GitHub stars
- 272
- Used in
- 3 other repos
- Token cost
- ~1.6k tokens
- SKILL.md length
- 653 words
- Files
- 1
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- MIT
At a glance
Interactive agent picker for composing and dispatching parallel teams
- Works in 5 steps: Discover Available Agents → Present Domain Menu → Handle Selection → …
- SKILL.md covers When to Use, Prerequisites, Configuration and How It Works, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Team Builder is an agent skill from loulanyue/awesome-claude-notes. Interactive agent picker for composing and dispatching parallel teams
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Community-maintained distribution of reusable AI coding agents, commands, skills, hooks, and cross-harness workflows. The licence is MIT.
Example prompts
- “/team-builder”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 866b55b. 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
Team Builder loads about 1.6k tokens when it runs. Until then it costs about 21 tokens; SKILL.md has 653 words of instructions outside code blocks.
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 loulanyue/awesome-claude-notes at commit 866b55b, republished under its MIT licence (© loulanyue). 653 words, ~1,575 tokens.
Download SKILL.mdSave it as
.claude/skills/team-builder/SKILL.md (or your agent's skills folder).- name
- team-builder
- description
- Interactive agent picker for composing and dispatching parallel teams
- origin
- community
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.mdFlat 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.mdConfiguration
Agent directories are probed in order and results are merged:
./agents/**/*.md+./agents/*.md— project-local agents (both depths)~/.claude/agents/**/*.md+~/.claude/agents/*.md— global agents (both depths)
Results from all locations are merged and deduplicated by agent name. Project-local agents take precedence over global agents with the same name. A custom path can be used instead if the user specifies one.
How It Works
Step 1: Discover Available Agents
Glob agent directories using the probe order above. Exclude README files. For each file found:
- 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.mdandengineering-software-architect.mdboth start withengineering→ 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 agent files are found after probing all locations, inform the user: "No agent files found. Checked: [list paths probed]. Expected: markdown files in one of those directories." 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
Show full SKILL.md (275 more words)Show less
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
- Read each selected agent's markdown file
- Prompt for the task description if not already provided
- 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
- 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: [...]© loulanyue, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/team-builder of loulanyue/awesome-claude-notes.
Open the folder on GitHubat commit 866b55b
Used in 3 other repositories
We found 8 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in loulanyue/awesome-claude-notes, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Team Builder 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Team Builder this skillloulanyue/awesome-claude-notes | 272 | 3 repos | ~1.6k | Automated safety check: Pass | MIT | |
| Team Builderaffaan-m/ECC | 275k | 1 repos | ~1.8k | Automated safety check: Pass | MIT | |
| Dispatching Parallel AgentsjnMetaCode/superpowers-zh | 8.3k | — | ~778 | Automated safety check: Pass | MIT | |
| Dispatching Parallel AgentsGanyuanRan/Aegis | 1.3k | 1 repos | ~972 | Automated safety check: Pass | MIT | |
| Parallel DispatchIbrahim-3d/orchestrator-supaconductor | 380 | — | ~4k | Automated safety check: Pass | AGPL-3.0 | |
| Parallels Discord Roundtripopenclaw/openclaw | 392k | — | ~788 | Automated safety check: Pass | MIT |
Similar skills
Dispatching Parallel Agents
jnMetaCode/superpowers-zh
当面对 2 个以上可以独立进行、无共享状态或顺序依赖的任务时使用
Dispatching Parallel Agents
GanyuanRan/Aegis
A skill your agent uses when facing 2+ independent tasks without a written plan, with no conflicting shared mutable state or sequential dependencies, where parallel delegation beats inline cost…
Parallel Dispatch
Ibrahim-3d/orchestrator-supaconductor
Parallel execution engine for dispatching worker agents. An agent skill from Ibrahim-3d/orchestrator-supaconductor.
Parallels Discord Roundtrip
openclaw/openclaw
Run macOS Parallels smoke with Discord send, host verification, host reply, and guest readback proof.
Openclaw Parallels Smoke
openclaw/openclaw
Prepare, snapshot, run, rerun, debug, or interpret OpenClaw Parallels guest install, onboarding, gateway smoke, and upgrade checks across macOS, Windows, and Linux.
More from loulanyue/awesome-claude-notes
All 9 skills in this repoClaude Devfleet
loulanyue/awesome-claude-notes
Orchestrate multi-agent coding tasks via Claude DevFleet — plan projects, dispatch parallel agents in isolated worktrees, monitor progress, and read structured reports.
Configure Ecc
loulanyue/awesome-claude-notes
Interactive installer for awesome claude notes — guides users through selecting and installing skills and rules to user-level or project-level directories, verifies paths, and optionally optimizes…
Claude API
loulanyue/awesome-claude-notes
Anthropic Claude API 的 Python 和 TypeScript 使用模式。涵盖 Messages API、流式处理、工具使用、视觉功能、扩展思维、批量处理、提示缓存和 Claude Agent SDK。适用于使用 Claude API 或 Anthropic SDK 构建应用程序的场景。
Configure Ecc
loulanyue/awesome-claude-notes
awesome claude notes のインタラクティブなインストーラー — スキルとルールの選択とインストールをユーザーレベルまたはプロジェクトレベルのディレクトリへガイドし、パスを検証し、必要に応じてインストールされたファイルを最適化します。
Configure Ecc
loulanyue/awesome-claude-notes
awesome claude notes 的交互式安装程序 — 引导用户选择并安装技能和规则到用户级或项目级目录，验证路径，并可选择优化已安装文件。
Project Guidelines Example
loulanyue/awesome-claude-notes
실제 프로덕션 애플리케이션을 기반으로 한 프로젝트별 스킬 템플릿 예시.
Questions about Team Builder
What does Team Builder do?
Interactive agent picker for composing and dispatching parallel teams. Team Builder is an agent skill from loulanyue/awesome-claude-notes.
How do I install Team Builder in Claude Code?
Run `npx skills add loulanyue/awesome-claude-notes --skill team-builder -a claude-code`. Or copy the skill folder (skills/team-builder in loulanyue/awesome-claude-notes) into .claude/skills/team-builder in your project. Claude Code loads it when a task matches its description.
How do I install Team Builder in Codex?
Run `npx skills add loulanyue/awesome-claude-notes --skill team-builder -a codex`. Or copy the skill folder (skills/team-builder in loulanyue/awesome-claude-notes) into .agents/skills/team-builder in your project. Codex loads it when a task matches its description.
Can I use Team Builder 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 loulanyue/awesome-claude-notes --skill team-builder -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-builder, .gemini/skills/team-builder, .github/skills/team-builder and .opencode/skills/team-builder in your project.
What does Team Builder need to run?
SKILL.md names no scripts, command-line tools or credentials: Team Builder is instructions for the agent only.
Does Team Builder 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 Builder 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 Team Builder use?
Team Builder 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 Builder use?
About 1.6k tokens (SKILL.md is roughly 6.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Team Builder?
Skills that share tags, products or a category with Team Builder: Team Builder (affaan-m/ECC, 275k stars), Dispatching Parallel Agents (jnMetaCode/superpowers-zh, 8.3k stars), Dispatching Parallel Agents (GanyuanRan/Aegis, 1.3k stars) and Parallel Dispatch (Ibrahim-3d/orchestrator-supaconductor, 380 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Team Builder?
loulanyue (a GitHub user) maintains it in loulanyue/awesome-claude-notes, which has 272 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 5, 2026.
Source: loulanyue/awesome-claude-notes on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.