Skip to content
Development
Skill

/coordinate

Kick off a multi-agent coordination task. Sends one email thread that CC's the whole team and lets them take turns.

From plugin
agenticmail
2493 skills1 MCP

Claude Code

$ npx -y skills add agenticmail/agenticmail --skill coordinate --agent claude-code

SKILL.md

coordinate.SKILL.md
description: Kick off a multi-agent coordination task. Sends one email thread that CC's the whole team and lets them take turns.
argument-hint: <task description>
allowed-tools: [mcp__agenticmail__list_agents, mcp__agenticmail__create_account, mcp__agenticmail__send_email, mcp__agenticmail__wait_for_email, mcp__agenticmail__list_inbox, mcp__agenticmail__read_email]

/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.
Read more
@agenticmail
Ships withagenticmail

Email, SMS & phone-call infrastructure for AI agents — send and receive real email and text messages, and place agent-driven outbound voice calls, all programmatically

2493 skills1 MCP
Get the whole plugin

Stars on GitHub

Momentum

stars in total
249
Star history of agenticmail/agenticmail on GitHub, a chart by star-history.com

Other skills on agenticmail.

More skills from other plugins.

brainstorming
Auto-invoked

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…

@obra@obraInstall Skill
ask-matt

ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

skills11d309k
@mattpocock@mattpocockInstall Skill
accessibility
Auto-invoked

accessibility

Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels,…

ecc13d293k
@affaan-m@affaan-mInstall Skill
compiler-commit

compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits…

react2d252k
@facebook@facebookInstall Skill

Questions about coordinate.

Which coding agents can use coordinate?
coordinate installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.