---
name: Coordinate
slug: coordinate
category: AI Engineering
description: Coordinate kicks off a multi-agent task in one email thread with everyone on CC. Use it when agents need to take turns, reply-all, and keep an audit trail of the work.
github: "https://github.com/agenticmail/agenticmail/tree/main/plugin/skills/coordinate"
language: TypeScript
stars: 216
forks: 35
install: "npx degit https://github.com/agenticmail/agenticmail/tree/main/plugin/skills/coordinate ~/.claude/skills/coordinate"
installs_to: ~/.claude/skills/coordinate
source_path: plugin/skills/coordinate/SKILL.md
collection_size: 4
category_size: 2970
collection_url: "https://dirskills.com/collections/agenticmail/agenticmail"
added: 2026-09-04T05:25:40.224Z
last_synced: 2026-09-04T05:25:40.224Z
canonical_url: "https://dirskills.com/skills/coordinate"
---

# Coordinate

Coordinate kicks off a multi-agent task in one email thread with everyone on CC. Use it when agents need to take turns, reply-all, and keep an audit trail of the work.

**Install:**

```bash
npx degit https://github.com/agenticmail/agenticmail/tree/main/plugin/skills/coordinate ~/.claude/skills/coordinate
```

## README

# /agenticmail-coordinate

Run a multi-agent task using the email thread pattern. This is how AgenticMail expects agents to coordinate. One thread, everyone on CC, agents take turns from context. Do not spawn native sub-agents to roleplay.

The user's task description is: $ARGUMENTS

## Steps

1. `mcp__agenticmail__list_agents` to see who exists. If the task needs specific roles that are not there, create them with `mcp__agenticmail__create_account` (give each one a clear role like "designer", "developer", "qa-reviewer").
2. Send one kickoff email with `mcp__agenticmail__send_email`. The first named actor goes on `to`. Everyone else, including the bridge identity, goes on `cc`. The body should:
   * Name each teammate and what step they own
   * Tell them to reply-all at each handoff
   * Tell them to do real work with native tools (write files, run code) not paste source into emails
3. Watch the thread with `mcp__agenticmail__wait_for_email` filtered on the thread subject. Surface each reply to the user as it lands.
4. Stop when the last handoff lands or the user says enough.

## Why this works

Every local recipient is auto-woken by the mail server when the kickoff lands. Each agent reads the full thread, sees who is CC'd, decides if it is their turn, and either reply-all's or stays silent. Turn-taking is implicit from context. The thread is a searchable audit trail.

## Do not

* Do not pass `_account: "<someone-else>"` from the host session, that falsifies the From header.
* Do not call `Agent { subagent_type: "..." }` and tell it to act as the AgenticMail agent. Send mail to them instead.
* Do not compose their reply yourself and send it on their behalf. Let them reply.