Agent skill · writing content · affaan-m
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.
Why this skill is useful
Provides a structured method for discovering and composing agent teams based on domain-specific markdown files, which the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-08-06. 238,342 stars on the source repository.
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: 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: 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills affaan-m/team-builder--743b27