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 rating
Deterministic checks triggered by the tool capabilities and evidence.
- Locality: Hybrid
Core control is local via iTerm2/mcporter, with optional Telegram API notifications.
- Data access: Sensitive
Exposes worker logs, task annotations, and project/worktree paths.
- Action surface: Execute
Spawns workers that can run code changes, commit worktree branches, and close issues.
Best practices
Follow these steps to reduce risk when using this skill.
- Use isolated worktrees and review each worker branch before merge/cherry-pick.
- Avoid enabling skip-permissions unless absolutely necessary for the task.
- Restrict notification credentials and rotate Telegram tokens used by monitoring scripts.
Evidence links
Public sources backing the indicator assignments.
Always be careful when navigating away from the website.
Max-risk rule
If any capability reaches a higher level, the entire indicator level bumps up to keep ratings deterministic and easy to scan.