Agent skill · software engineering · sundial-org
claude-team
Orchestrate multiple Claude Code workers via iTerm2 using the claude-team MCP server. Spawn workers with git worktrees, assign beads issues, monitor progress, and coordinate parallel development work.
Why this skill is useful
Adds specific commands and workflows for managing Claude Code sessions that the AI wouldn't generate on its own.
What it needs
Requires mcporter installed locally. About 6k tokens when loaded. Last updated 2026-03-07. 639 stars on the source repository.
What this skill does
Claude Team Claude-team is an MCP server that lets you spawn and manage teams of Claude Code sessions via iTerm2. Each worker gets their own terminal pane, optional git worktree, and can be assigned beads issues. Why Use Claude Team? Parallelism: Fan out work to multiple agents working simultaneously Context isolation: Each worker has fresh context, keeps coordinator context clean Visibility: Real Claude Code sessions you can watch, interrupt, or take over Git worktrees: Each worker can have an isolated branch for their work ⚠️ Important Rule NEVER make code changes directly. Always spawn workers for code changes. This keeps your context clean and provides proper git workflow with worktrees. Prerequisites macOS with iTerm2 (Python API enabled: Preferences → General → Magic → Enable Python API) claude-team MCP server configured in ~/.claude.json Using via mcporter All tools are called through mcporter call claude-team.<tool>: Core Tools spawnworkers Create new Claude Code worker sessions. Worker config fields: projectpath: Required. Path to repo or "auto" (uses CLAUDETEAMPROJECTDIR) bead: Optional beads issue ID — worker will follow beads workflow annotation: Task description (shown on badge, used in branch name) prompt: Additional instructions (if no bead, this is their assignment) useworktree: Create isolated git worktree (default: true) skippermissions: Start with --dangerously-skip-permissions (default: false) name: Optional worker name override (auto-picks from themed sets otherwise) Layout options: "auto": Reuse existing claude-team windows, split into available space "new": Always create fresh window (1-4 workers in grid layout) listworkers See all managed workers: Status values: spawning, ready, busy, closed messageworkers Send messages to one or more workers: waitmode options: "none": Fire and forget (default) "any": Return when any worker is idle "all": Return when all workers are idle checkidleworkers / waitidleworkers Check or wait for workers to finish: …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sundial-org/claude-team