team-builder
Interactive agent picker for composing and dispatching parallel teams
Security Assessment
About team-builder
The team-builder skill is designed to streamline the process of assembling specialized teams from a pool of AI agents, each defined by distinct personas. It addresses the challenge of managing multiple agents across different domains, allowing users to browse, select, and compose parallel teams efficiently for a given task. By providing an interactive menu, it simplifies the discovery and selection of agents, ensuring that teams are tailored to specific project needs without manual tracking of individual agent capabilities or domains.
This skill offers several key features. It supports both flat and subdirectory layouts for agent organization, automatically inferring domains either from folder structures or filename prefixes. Agents are sourced from multiple origins, including the CLI via the `claude agents` command, local project files, and global user files, with a clear precedence order to resolve conflicts. The system extracts agent names and descriptions from markdown files, and it dynamically generates domain-based menus for easy selection. Plugin agents, user agents, and built-in agents are all accommodated, providing a unified interface to manage diverse agent collections.
Team-builder is ideal for users who work with multiple agent personas and require ad-hoc team composition across various domains such as engineering, marketing, or sales. It is particularly useful for those needing to explore available agents before task assignment, for creating domain-specific or cross-functional teams, and for rapidly deploying specialized agents without manual configuration. Target users include developers, project managers, and anyone leveraging AI agents in collaborative or multi-domain environments.
FAQ
How do I add new agents to be available in team-builder?
Agents must be markdown files containing a persona prompt. Place them in the `./agents/` folder for project-local agents or `~/.claude/agents/` for global access. Ensure each file has a `# Heading` for the agent name and a first paragraph for the description.
Can team-builder work with agents organized in subdirectories and flat layouts?
Yes, subdirectory layouts infer domains from folder names, while flat layouts use filename prefixes. Prefixes only count as domains if shared by two or more files; otherwise, files go into the 'General' domain.
Which agents are discovered first when there are duplicates?
User agents take precedence over plugin agents, which take precedence over built-in agents. The earlier source is used if agent names collide.
What happens if no agents are found?
The system informs the user: 'No agents found. Run `claude agents` to verify your setup.' No further actions are taken until agents are available.
Does team-builder include built-in agents automatically?
Built-in agents are skipped unless the user explicitly requests to include them in the agent list.
Install team-builder
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
affaan-m/everything-claude-code