Claude Team

The stated purpose (orchestrating Claude Code workers via iTerm2) matches many of the instructions (creating worktrees, controlling iTerm2, spawning workers). However the SKILL.md metadata and text require tools not declared in the registry metadata: it references 'mcporter', 'uvx', the 'bd' (beads) CLI, iTerm2 Python API, and a ~/.claude.json config. The registry lists no required binaries or env vars — that mismatch is incoherent and unexplained.

Instructions tell the agent to create git worktrees, run bd show, mark/close issues, commit changes, and run workers with a '--dangerously-skip-permissions' option. They also expect access to user repositories (project_path), ~/.claude.json, and the iTerm2 Python API (which grants control over the terminal). These actions are powerful and go beyond simple orchestration; the documentation does not declare what credentials or protections are used when workers perform issue state changes or commits.

There is no formal install spec in the registry, but a provided assets/setup.sh configures a launchd service and expects a plist template 'com.claude-team.plist.template' that is not included in the bundle. setup.sh checks for 'uvx' and directs users to install it via a curl | sh script from astral.sh — fetching and running remote install scripts is high risk. The combination of a missing template and an external install instruction is an integrity/availability concern.

The skill declares no required env vars or primary credential, yet the instructions reference configuration files (~/.claude.json), an implied CLAUDE_TEAM_PROJECT_DIR, and rely on local CLIs (mcporter, bd) which likely need their own credentials/config. In addition, the guidance to use '--dangerously-skip-permissions' suggests bypassing safety controls without justification. Credentials or tokens for issue systems, git remotes, or the MCP server are not described but would be necessary in practice.

always is false (good), but the bundled setup.sh installs a persistent launchd agent (writes to ~/Library/LaunchAgents and loads it). Installing that service requires user approval and grants continuous local network capability (server listening on 127.0.0.1:8766 in examples). Persisting a service is expected for a local MCP server but is a material change to the system and should only be done after inspecting the missing plist template and the server binary invoked by uvx.