claude-teams

Included with Lifetime

$97 forever

Guide for coordinating multiple Claude Code agents as teams. Use when setting up agent teams, configuring subagents, orchestrating multi-agent workflows, or building programmatic agent systems with the Claude Agent SDK.

Backend & APIs

What this skill does

# Claude Teams

Coordinate multiple Claude Code agents working together on shared tasks.

## When forming a team

Invoke `/core:agent-loop` for the 4-phase / 6-tier execution model.
Invoke `/claude-code:claude-agents` for agent file format, tool allowlists, and model selection.
Invoke `/core:anti-fabrication` always — every claim about a tool, file, or test result requires tool execution.

Require each teammate to quote one sentence from each loaded skill in its first message as proof of loading. Do not proceed with the teammate's work until proof is received.

Glob patterns like `/core:*` do not expand in Agent prompts. List skill names explicitly.

## When to Use

Activate when:
- Setting up or configuring Agent Teams (experimental)
- Creating custom subagents for task delegation
- Building multi-agent workflows with the Claude Agent SDK
- Designing coordination patterns for parallel agent work
- Troubleshooting agent communication or task assignment

## Approaches

Three approaches exist for multi-agent coordination, each with different trade-offs:

| Approach | Communication | Coordination | Best For |
|----------|--------------|--------------|----------|
| **Agent Teams** | Peer-to-peer messaging + shared task list | Team lead + self-coordination | Collaborative work requiring discussion |
| **Subagents** | Report back to parent only | Parent manages all | Focused delegated tasks |
| **Agent SDK** | Programmatic message streaming | Developer-controlled | CI/CD, automation, custom apps |

## Agent Teams (Experimental)

First-party multi-agent coordination. A team lead spawns teammates that work independently with peer-to-peer messaging and a shared task list.

Enable with: `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1`

For setup, configuration, and usage details, see `references/agent-teams.md`.

## Subagents (Task Tool)

Lightweight delegation within a single session. Subagents run in their own context window, complete a task, and return results to the parent.

For subagent types, custom agents, and isolation patterns, see `references/subagents.md`.

## Agent SDK

Programmatic multi-agent orchestration in Python and TypeScript using the same tools that power Claude Code.

For SDK setup, agent definitions, and session management, see `references/agent-sdk.md`.

## Multi-Agent Patterns

Proven patterns for file ownership, task decomposition, scaling, and quality gates.

For architecture guidance and case studies, see `references/patterns.md`.

## Orchestration primitives

`/core:agent-loop` defines the decomposition + delegation flow. Three Claude Code primitives compose with it for long-running or recurring work:

| Primitive | Use when |
|---|---|
| `/loop <prompt>` | You want a self-pacing tick: monitor agents, poll the tracker, advance the queue. Auto-paces via ScheduleWakeup. |
| Routines | Cron-style scheduled remote agents. Use for daily/weekly autonomous runs. |
| Channels | Event-driven (webhook/integration) entry points. Use when an external system kicks the loop. |

There is no `/workflows` slash command in Claude Code. For multi-step orchestration, compose the above with `/core:agent-loop`.

### /loop example — shepherd a running epic

After dispatching a team for an epic, the operator session runs:

```
/loop /shepherd
```

where `/shepherd` is a project-defined command (not shipped with this plugin — define it in your project's `.claude/commands/`) that, each tick:

1. Reads bees/tracker state for the epic's issues
2. Promotes ready issues to in_progress
3. Notifies the operator if any agent transitioned to a review or needs_help state
4. Halts and pings via PushNotification when the cohort is complete

The `/loop` harness auto-paces via ScheduleWakeup (default 270s — stays inside the prompt-cache TTL). The operator session is hands-off until the loop fires a notification.

This is the recommended composition for long-running multi-agent work: `/core:agent-loop` does the per-spawn discipline; `/loop` does the queue advancement.

Files: 5

Size: 19.6 KB

Complexity: 41/100

Category: Backend & APIs

Source: https://github.com/vinnie357/claude-skills/tree/main/plugins/tools/claude-code/skills/claude-teams

Related in Backend & APIs

jfrog

Included

Interact with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.

Backend & APIsscripts

cupynumeric-migration-readiness

Included

Pre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.

Backend & APIsscripts

alibabacloud-data-agent-skill

Included

Invoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".

Backend & APIsscripts

token-optimizer

Included

Reduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.

Backend & APIsscripts

resend-cli

Included

Use this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.

Backend & APIsscripts

alibabacloud-odps-maxframe-coding

Included

Use this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.

Backend & APIsscripts