Cooper Send Email
Send, reply to, forward, draft, or schedule email from a Cooper Email (cooperemail.com) inbox through the connected Cooper MCP server, with idempotent sends so a retry never sends twice. Use for ANY request to send, reply, or forward mail from a Cooper inbox, even a one-line send; the sending rules apply regardless of task size. Do not use for reading or triage (cooper-check-email), inbox administration (cooper-manage-inboxes), or MCP setup (cooper-mcp). If the user asked for Cooper Email, do not substitute another mail API.
Install
/plugin marketplace add cooper-email/cooper-emailThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add cooper-email/cooper-email --skill cooper-send-emailgit clone --depth 1 https://github.com/cooper-email/cooper-email.git /tmp/cooper-email
mkdir -p ~/.claude/skills
cp -r /tmp/cooper-email/skills/cooper-send-email ~/.claude/skills/cooper-send-emailPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Send email with Cooper Real email leaves immediately and cannot be recalled. Prepare it without guessing anything a recipient will see. ## Choose the operation - "Write", "compose", or "prepare" means a draft: `cooper_create_draft`. - "Send", "reply", or "forward" authorizes a send only when the sender inbox, recipients (or the message being answered), subject, and body are explicit or already confirmed. - New mail: `cooper_send_message`. Reply in the thread: `cooper_reply_message` (`reply_all: true` adds the other original To and Cc). Forward with the original attachments: `cooper_forward_message`. - Approved draft: `cooper_send_draft`. Scheduled send: `cooper_create_draft` with `send_at`; cancel with `cooper_delete_draft`. - Replies and forwards take a `message_id`, never a thread id. ## Execute safely 1. Resolve the sending inbox with `cooper_list_inboxes` if the user did not name one. Ask when several fit. Do not create an inbox unless asked. 2. For a reply or forward, read the conversation (`cooper_get_thread`) and pick the exact message id. 3. Keep the user's meaning. Do not invent recipients, attachments, claims, signatures, or commitments. 4. If any visible field was inferred, show sender, recipients, subject, body, and attachments, and ask before sending. 5. Always pass an idempotency key: `idempotency_key` on `cooper_send_message`, `cooper_send_draft`, and `cooper_reply_task`, or `client_id` on send, reply,
Details
- Skill name
cooper-send-email- Repository
- cooper-email/cooper-email
- Path
skills/cooper-send-email/SKILL.md- License
- MIT
- Repo updated
- 14 November 2026
- Listed in
- karanb192/awesome-claude-skills
FAQ
What does the Cooper Send Email skill do?
Send, reply to, forward, draft, or schedule email from a Cooper Email (cooperemail.com) inbox through the connected Cooper MCP server, with idempotent sends so a retry never sends twice. Use for ANY request to send, reply, or forward mail from a Cooper inbox, even a one-line send; the sending rules apply regardless of task size. Do not use for reading or triage (cooper-check-email), inbox administration (cooper-manage-inboxes), or MCP setup (cooper-mcp). If the user asked for Cooper Email, do not substitute another mail API.
How do I install the Cooper Send Email skill?
Claude Code plugin: /plugin marketplace add cooper-email/cooper-email. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Related skills
Agent Email
cooper-email/cooper-email
Give the agent its own email address with Cooper Email. Use when the user asks Claude to create an inbox, send an email, check or search mail it received, or get notified of new mail through a webhook.
Cooper Agent Email Patterns
cooper-email/cooper-email
Architecture patterns for AI agents that use email, built on Cooper Email (cooperemail.com) - one inbox per agent, temporary inboxes per run, two-way reply loops, owner-approved sends, owner updates and email tasks, verification-code flows, webhooks vs long-polling, suppressions and bounces, idempotent sends, and the threat model (prompt injection, spoofed senders, leaked keys). Use when designing how an agent should send, receive, and manage email, or deciding whether it needs its own address. Not for single tool calls; use the action skills for those.
Cooper Agent Inbox
cooper-email/cooper-email
Basics of an AI agent's own email inbox on Cooper Email (cooperemail.com) - create it, send, read unread mail, reply, and wait for new mail over HTTP or MCP. Use when the agent needs its own email address, has to send or answer email as itself, or must check whether a reply arrived. If the user asked for Cooper Email, do not substitute another mail API.
Cooper Suppressions Bounces
cooper-email/cooper-email
Handle bounces, spam complaints, and the suppression list for Cooper Email (cooperemail.com) agent inboxes - see which addresses Cooper will not email and why, react to bounce and complaint events, check bounce and complaint rates, and restore an address only when the user confirms it is good. Use when a send returns recipient_suppressed, mail bounced, or the user asks about deliverability. If the user asked for Cooper Email, do not substitute another mail API.
Cooper Owner Updates
cooper-email/cooper-email
Keep a human owner in the loop by email with Cooper Email (cooperemail.com) - send progress, done, blocker, and question updates (immediately or as a daily digest), receive the owner's emailed replies as authenticated tasks, and answer them in the same thread. Use for long-running agent work where a person should get status by email and can reply with instructions, or when the agent needs a human's answer to continue. If the user asked for Cooper Email, do not substitute another mail API.
Cooper Webhooks
cooper-email/cooper-email
Get pushed the moment mail arrives in a Cooper Email (cooperemail.com) inbox with one call - register, verify signatures, filter events and inboxes, test, disable, and remove webhooks. Covers message, task, owner, domain, and draft-approval events. Use when the user has a public HTTPS endpoint (their server, Zapier, Make, n8n) and wants push instead of polling, or a webhook is failing. If the user asked for Cooper Email, do not substitute another mail API.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.