team-builder by affaan-m/everything-claude-code
npx skills add https://github.com/affaan-m/everything-claude-code --skill team-builder用于按需浏览和组合智能体团队的交互式菜单。支持扁平化或按领域子目录组织的智能体集合。
智能体文件必须是包含角色提示(身份、规则、工作流程、交付成果)的 Markdown 文件。第一个 # 标题 被用作智能体名称,第一个段落被用作描述。
支持扁平化和子目录两种布局:
子目录布局 — 领域从文件夹名称推断:
agents/
├── engineering/
│ ├── security-engineer.md
│ └── software-architect.md
├── marketing/
│ └── seo-specialist.md
└── sales/
└── discovery-coach.md
扁平布局 — 领域从共享的文件名前缀推断。当 2 个或更多文件共享同一前缀时,该前缀被视为一个领域。具有唯一前缀的文件归入 "General" 类别。注意:算法在第一个 - 处分割,因此多单词领域(例如 product-management)应使用子目录布局:
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
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
智能体目录按顺序探测,结果合并:
./agents/**/*.md + ./agents/*.md — 项目本地智能体(两种深度)~/.claude/agents/**/*.md + ~/.claude/agents/*.md — 全局智能体(两种深度)所有位置的结果按智能体名称合并并去重。同名的项目本地智能体优先于全局智能体。如果用户指定了自定义路径,则使用该路径。
使用上述探测顺序对智能体目录进行全局搜索。排除 README 文件。对于找到的每个文件:
- 之前的文本)。一个前缀只有在出现在 2 个或更多文件名中时才符合领域资格(例如,engineering-security-engineer.md 和 engineering-software-architect.md 都以 engineering 开头 → Engineering 领域)。具有唯一前缀的文件(例如 code-reviewer.md、tdd-guide.md)归入 "General" 类别# 标题 提取智能体名称。如果未找到标题,则从文件名派生名称(去除 .md,用空格替换连字符,转换为标题大小写)如果在探测所有位置后未找到智能体文件,则通知用户:"未找到智能体文件。已检查:[探测的路径列表]。期望:这些目录之一中的 Markdown 文件。" 然后停止。
可用智能体领域:
1. Engineering — Software Architect, Security Engineer
2. Marketing — SEO Specialist
3. Sales — Discovery Coach, Outbound Strategist
选择领域或指定具体智能体(例如:"1,3" 或 "security + seo"):
接受灵活的输入:
如果选择的智能体超过 5 个,则按字母顺序列出它们,并要求用户缩小范围:"您选择了 N 个智能体(最多 5 个)。选择保留哪些,或说 'first 5' 以使用按字母顺序排列的前五个。"
确认选择:
已选择:Security Engineer + SEO Specialist
他们应该处理什么?(描述任务):
subagent_type: "general-purpose"prompt: "{agent file content}\n\nTask: {task description}"收集所有输出并呈现统一报告:
如果只选择了 1 个智能体,则跳过综合部分,直接呈现输出。
User: team builder
Claude:
可用智能体领域:
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
选择领域或指定具体智能体:
User: security + seo
Claude:
已选择:Security Engineer + SEO Specialist
他们应该处理什么?
User: 在发布前审查我的 Next.js 电子商务网站
[两个智能体并行启动,各自将其专长应用于代码库]
Claude:
## Security Engineer 发现
- [发现...]
## SEO Specialist 发现
- [发现...]
## 综合
两个智能体都同意:[...]
矛盾点:安全建议的 CSP 会阻止内联样式,SEO 需要内联模式标记。解决方案:[...]
后续步骤:[...]
每周安装量
306
代码仓库
GitHub 星标数
102.1K
首次出现
8 天前
安全审计
安装于
codex291
cursor258
github-copilot255
gemini-cli255
opencode255
cline255
Interactive menu for browsing and composing agent teams on demand. Works with flat or domain-subdirectory agent collections.
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
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.
Glob agent directories using the probe order above. Exclude README files. For each file found:
-). 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"# Heading. If no heading is found, derive the name from the filename (strip .md, replace hyphens with spaces, title-case)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.
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"):
Accept flexible input:
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):
subagent_type: "general-purpose"prompt: "{agent file content}\n\nTask: {task description}"Collect all outputs and present a unified report:
If only 1 agent was selected, skip synthesis and present the output directly.
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: [...]
Weekly Installs
306
Repository
GitHub Stars
102.1K
First Seen
8 days ago
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
codex291
cursor258
github-copilot255
gemini-cli255
opencode255
cline255
AI Elements:基于shadcn/ui的AI原生应用组件库,快速构建对话界面
54,900 周安装