plugin/skills/coordinate/SKILL.md
Kick off a multi-agent coordination task. Sends one email thread that CC's the whole team and lets them take turns.
npx skillsauth add agenticmail/agenticmail plugin/skills/coordinateInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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
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").mcp__agenticmail__send_email. The first named actor goes on to. Everyone else, including the bridge identity, goes on cc. The body should:
mcp__agenticmail__wait_for_email filtered on the thread subject. Surface each reply to the user as it lands.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.
_account: "<someone-else>" from the host session, that falsifies the From header.Agent { subagent_type: "..." } and tell it to act as the AgenticMail agent. Send mail to them instead.tools
🎀 AgenticMail — Full email, SMS, storage & multi-agent coordination for AI agents. 63 tools.
tools
Install and bootstrap AgenticMail (one-time setup that gives every agent a real email address)
tools
Create a new AgenticMail agent with a name and a role, ready to coordinate with others over email
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.