← ClaudeAtlas

team-agentlisted

Use only when the user explicitly asks to start, operate, inspect, shutdown, or restart a Team Agent team. Treat the team-agent CLI as a sealed appliance.
Florious95/team-agent · ★ 7 · AI & Automation · score 71
Install: claude install-skill Florious95/team-agent
# Team Agent Sealed appliance for someone who just got the CLI. Operator handbook (permissions, models, routing, recovery): `references/team-agent-operator.md`. If `team-agent --version` does not match `last_verified_against`, do not copy examples as current truth. Learn from the live CLI: ```bash team-agent --version team-agent --help team-agent doctor --help ``` **Launch** from a tmux-addressable pane: `team-agent claude` or `team-agent codex`, then `team-agent quick-start .team/current`. Do not start a real team from a naked terminal. Existing tmux/Ghostty layouts are valid if `quick-start` runs from the leader pane. **Operate** - Dispatch: `team-agent send TO MESSAGE` (positional TO; `--watch-result` is deprecated). After success, do not poll with `sleep` / `status` / `inbox` / `collect`. TO has two co-equal logical forms: an **in-team short name** (`team-agent send reviewer "..."`) and a fully qualified `<workspace>::<team>/<agent>`. Use the qualified form across workspaces. - Inspect: `team-agent status` / `status --json`. `ok: true` plus `ready: false` is not a crash. - Lifecycle: `restart .` resumes a stopped team; `add-agent NAME --role-file FILE` adds or `--force` recreates one worker; `shutdown --workspace .` stops. Do not shutdown the whole team to add a worker. - Roles: every `agents/*.md` must declare boolean `dangerously_skip_permissions`. Never rewrite a user-supplied model id. Never read `.env` files. **On failure:** if the CLI prints a structured `a