team
Spawn long-lived provider LLM teammates in tmux panes that you message via the native agent-team tools — multi-turn, collaborative, watchable. Use for sustained parallel build/work ("spawn workers", N teammates on N files), or when you need a collaborator you message across turns. NOT a fire-and-forget one-shot or a flat batch of independent prompts — that is /cc-fleet:subagent. NOT a scripted multi-phase run — that is /cc-fleet:workflow.
npx skills add ethanhq/cc-fleet --skill team --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# team — long-lived provider teammates Run a third-party provider model as a real Claude Code teammate in a tmux pane: same tool stack and team coordination as a native teammate, LLM backend swapped to the provider. Your main session's own auth stays untouched. **Wrong lane?** A fire-and-forget one-shot or flat batch → /cc-fleet:subagent; a scripted multi-phase run → /cc-fleet:workflow; full arbitration in cc-fleet-shared/routing.md. When this skill cites `cc-fleet-shared/<file>.md`, OPEN it with the Read tool at `../cc-fleet-shared/<file>.md` relative to this SKILL.md — the cited content is load-bearing, not optional background. > **Execution environment — check before running anything.** Confirm your shell tool executes on the host where cc-fleet is installed. In sandboxed or remote agent sessions, a tool named Bash may run on an isolated machine with a different filesystem, PATH, processes, and tmux server — `command not found`, a healthy-looking `doctor` whose leaves can't reach your files, or a wrong working directory should prompt you to verify whether you are in a sandbox shell, not conclude that cc-fleet is broken. If so, route commands through a host-executing bridge tool
- Core loop
- Example: one worker on a refactor
- Example: three workers in parallel
- The provider ask ladder (ask at most once per task)
- Getting a teammate's result back
- Watching for stuck teammates
- Acting on a wedged teammate
- Where a teammate runs (in-tmux split vs out-of-tmux swarm)
- Hiding / showing a pane (in-tmux only)
- Anti-patterns
cc-fleet spawn --as worker-1 --team refactor-api --model strong --json # default provider cc-fleet teardown refactor-api --json # Bash, FIRST cc-fleet spawn kimi --as zh-1 --team translate-docs --json # leaf: omit --model cc-fleet spawn kimi --as zh-2 --team translate-docs --json cc-fleet spawn deepseek --as polish --team translate-docs --model strong --json # synthesis: strong cc-fleet teardown translate-docs --json # FIRST: kills all three panes + procs cc-fleet ps --json # → the teammate's tmux_socket + pane_id tmux -L <tmux_socket> capture-pane -t <pane_id> -p | tail -40 cc-fleet hide <target> --json # pane → detached "claude-hidden" session; keeps running cc-fleet show <target> --json # pane → back to its origin window, re-tiled
What does the team skill do?
Spawn long-lived provider LLM teammates in tmux panes that you message via the native agent-team tools — multi-turn, collaborative, watchable. Use for sustained parallel build/work ("spawn workers", N teammates on N files), or when you need a collaborator you message across turns. NOT a fire-and-forget one-shot or a flat batch of independent prompts — that is /cc-fleet:subagent. NOT a scripted multi-phase run — that is /cc-fleet:workflow.
How do I install it?
Run `npx skills add ethanhq/cc-fleet --skill team --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ethanhq/cc-fleet, a repository with 201 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.