How do I install the Teams skill?

Run npx skillmds@latest add aibot88/teams in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Teams safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Teams?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Teams free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

aibot88 (@aibot88) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Teams by aibot88 — Agent Skill

Name: Teams
Rating: 4.2 (5 reviews)
Author: aibot88

Teams

Launches pre-configured multi-agent teams for code review, debugging, feature development, security audits, and database migrations. Use when the user asks to start a multi-agent workflow, coordinate agent teams, run a team review, or needs parallel agent collaboration on a complex task.

aibot88 Updated Sep 9, 2026 3 repo stars

File contents

/teams: Agent Teams Presets

$ARGUMENTS

Launches a pre-configured Agent Teams composition for your task. Requires CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1.

Available Presets

Preset	Agents	Use Case
`review`	code-reviewer, security-auditor, performance-optimizer	PR code review
`debug`	debugger, backend-specialist, incident-responder	Multi-file bug investigation
`feature`	orchestrator, backend-specialist, frontend-specialist, test-engineer	Full feature implementation
`fullstack`	backend-specialist, frontend-specialist, database-architect, devops-implementer	Full-stack task
`research`	technical-researcher, data-analyst, prompt-engineer	Deep research task
`security`	security-architect, security-auditor, backend-specialist	Security audit
`migration`	database-architect, backend-specialist, devops-implementer	Database migration

See reference/presets.md for detailed ownership, aggregation strategies, and output formats for each preset.

Usage

/teams review              # Launch review team on current changes
/teams debug               # Launch debug team for current issue
/teams feature add auth    # Launch feature team with task context
/teams security            # Launch security audit team

Workflow

Parse $ARGUMENTS: extract <preset> and optional [task-description]
Validate preset is one of: review, debug, feature, fullstack, research, security, migration
Check environment: verify CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS is set; warn if missing
Display team composition and ownership rules from reference/presets.md
Confirm with user before launching

Launch agents: spawn each agent with its assigned scope using the Agent tool:

Agent({ description: "code-reviewer: PR review lead", prompt: "[task + ownership rules]" })
Agent({ description: "security-auditor: security findings", prompt: "[task + domain scope]" })

Aggregate results: apply the preset's aggregation strategy (consensus, relay, or map-reduce)
Produce output: write the defined output document (e.g., REVIEW.md, DEBUG_REPORT.md)

Error Handling

If an agent fails or times out: log the failure, continue with remaining agents, note the gap in the output
If agents produce conflicting findings: the lead agent resolves conflicts; flag unresolved disagreements for user review

Environment

export CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1

---name: teamsdescription: Launches pre-configured multi-agent teams for code review, debugging, feature development, security audits, and database migrations. Use when the user asks to start a multi-agent workflow, coordinate agent teams, run a team review, or needs parallel agent collaboration on a complex task.--- # /teams: Agent Teams Presets $ARGUMENTS Launches a pre-configured Agent Teams composition for your task. Requires `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1`. ## Available Presets | Preset | Agents | Use Case | |--------|--------|----------| | `review` | code-reviewer, security-auditor, performance-optimizer | PR code review | | `debug` | debugger, backend-specialist, incident-responder | Multi-file bug investigation | | `feature` | orchestrator, backend-specialist, frontend-specialist, test-engineer | Full feature implementation | | `fullstack` | backend-specialist, frontend-specialist, database-architect, devops-implementer | Full-stack task | | `research` | technical-researcher, data-analyst, prompt-engineer | Deep research task | | `security` | security-architect, security-auditor, backend-specialist | Security audit | | `migration` | database-architect, backend-specialist, devops-implementer | Database migration | See [reference/presets.md](reference/presets.md) for detailed ownership, aggregation strategies, and output formats for each preset. ## Usage ``` /teams review # Launch review team on current changes /teams debug # Launch debug team for current issue /teams feature add auth # Launch feature team with task context /teams security # Launch security audit team ``` ## Workflow 1. **Parse** `$ARGUMENTS`: extract `<preset>` and optional `[task-description]` 2. **Validate** preset is one of: review, debug, feature, fullstack, research, security, migration 3. **Check environment**: verify `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS` is set; warn if missing 4. **Display** team composition and ownership rules from [reference/presets.md](reference/presets.md) 5. **Confirm** with user before launching 6. **Launch agents**: spawn each agent with its assigned scope using the Agent tool: ``` Agent({ description: "code-reviewer: PR review lead", prompt: "[task + ownership rules]" }) Agent({ description: "security-auditor: security findings", prompt: "[task + domain scope]" }) ``` 7. **Aggregate results**: apply the preset's aggregation strategy (consensus, relay, or map-reduce) 8. **Produce output**: write the defined output document (e.g., `REVIEW.md`, `DEBUG_REPORT.md`) ### Error Handling - If an agent fails or times out: log the failure, continue with remaining agents, note the gap in the output - If agents produce conflicting findings: the lead agent resolves conflicts; flag unresolved disagreements for user review ## Environment ```bash export CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 ```

Frequently asked questions