Team Management
This skill should be used when the user asks to "manage teams", "create a team", "create a task", "assign a task", "send a message to an agent", "list teams", "check tasks", "broadcast to team", "read inbox", "update task status", or any team/task/agent/message management operation.
What this skill does
# Team Management
Use the team-overlord MCP tools to manage Claude Code agent teams, tasks, and messages.
## Available Tools
### Read-only
- **list_teams** — List all teams with members and status
- **get_team(team)** — Get full team configuration
- **list_tasks(team, status?)** — List tasks, optionally filtered by status (`pending`, `in_progress`, `completed`)
- **get_task(team, task_id)** — Get a single task by ID
- **read_inbox(team, agent)** — Read an agent's message inbox
### Write
- **create_team(name, description?)** — Create a new team with directories and config
- **create_task(team, subject, description?)** — Create a task (auto-increments ID)
- **update_task(team, task_id, status?, owner?, subject?, description?)** — Update task fields (only non-empty values are changed)
- **send_message(team, to, text)** — Send a message to a specific agent
- **broadcast_message(team, text)** — Send a message to all agents in a team
## Data Schemas
### Team Config (`~/.claude/teams/<name>/config.json`)
```json
{
"name": "team-name",
"description": "",
"createdAt": 1710000000000,
"leadAgentId": "name@team",
"leadSessionId": "uuid",
"members": [
{
"agentId": "name@team",
"name": "agent-name",
"agentType": "worker",
"model": "sonnet",
"color": "blue",
"cwd": "/path/to/project"
}
]
}
```
### Task (`~/.claude/tasks/<team>/<id>.json`)
```json
{
"id": "1",
"subject": "Task title",
"description": "Detailed description",
"status": "pending|in_progress|completed",
"owner": "agent-name",
"blocks": ["2"],
"blockedBy": []
}
```
### Inbox Message (`~/.claude/teams/<team>/inboxes/<agent>.json`)
Array of messages:
```json
{
"from": "sender-name",
"text": "message content",
"timestamp": "ISO 8601",
"read": false,
"summary": "optional preview",
"color": "optional badge color"
}
```
## Common Workflows
### Create a team and set up tasks
1. `create_team("my-team", "Building feature X")`
2. `create_task("my-team", "Implement auth", "Add JWT authentication...")`
3. `update_task("my-team", "1", owner="researcher")`
### Monitor progress
1. `list_teams()` — overview of all teams
2. `list_tasks("my-team", "in_progress")` — what's being worked on
3. `read_inbox("my-team", "researcher")` — check agent's messages
### Communicate with agents
1. `send_message("my-team", "researcher", "Please prioritize the auth task")`
2. `broadcast_message("my-team", "Stand down — merging to main now")`
## Context
Each prompt includes a `<team-context>` block showing current team state (members, statuses, task counts). Use the tools to act on this state — the context block is read-only and reflects the latest disk state.
## Limitations
- **Spawning/killing agents** requires the TUI's AgentManager (live SDK sessions). Use `/spawn` and `/kill` commands for those operations.
- All data is stored as JSON under `~/.claude/`. Changes are immediately visible to the TUI via filesystem watching.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.