create-agent
Create a new AgenticMail agent with a name and a role, ready to coordinate with others over email
Kick off a multi-agent coordination task. Sends one email thread that CC's the whole team and lets them take turns.
Claude Code
$ npx -y skills add agenticmail/agenticmail --skill coordinate --agent claude-code
Codex
$ npx skills add agenticmail/agenticmail --skill coordinate -a codex -y
Cursor
$ npx skills add agenticmail/agenticmail --skill coordinate -a cursor -y
Gemini CLI
$ npx skills add agenticmail/agenticmail --skill coordinate -a gemini-cli -y
GitHub Copilot
$ npx skills add agenticmail/agenticmail --skill coordinate -a github-copilot -y
OpenCode
$ npx skills add agenticmail/agenticmail --skill coordinate -a opencode -y
Windsurf
$ npx skills add agenticmail/agenticmail --skill coordinate -a windsurf -y
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]
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
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:
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.
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.
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
Create a new AgenticMail agent with a name and a role, ready to coordinate with others over email
Install and bootstrap AgenticMail (one-time setup that gives every agent a real email address)
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.