Cooper Idempotent Sends

Make every Cooper Email (cooperemail.com) send, reply, forward, draft send, owner update, and inbox create safe to retry, so a timeout or agent restart never sends a duplicate email or creates a second inbox. Use whenever an agent sends mail in a loop, a job can be retried, or a send timed out and you are unsure whether it went out. If the user asked for Cooper Email, do not substitute another mail API.

Productivity & Notes Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add cooper-email/cooper-email

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add cooper-email/cooper-email --skill cooper-idempotent-sends
Manual install
git 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-idempotent-sends ~/.claude/skills/cooper-idempotent-sends

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Idempotent sends with Cooper

Email cannot be recalled, so a blind retry can mail someone twice. Cooper
accepts a key on every write; a repeat with the same key returns the original
result instead of acting again.

## Which key to pass

| Action | MCP tool | Key |
| --- | --- | --- |
| New message | `cooper_send_message` | `idempotency_key` or `client_id` |
| Reply / forward | `cooper_reply_message`, `cooper_forward_message` | `client_id` |
| Send a draft | `cooper_send_draft` | `idempotency_key` |
| Reply to a task | `cooper_reply_task` | `idempotency_key` (without it, two calls send two emails) |
| Owner update | `cooper_notify_owner` | `client_id` |
| Create inbox / draft / webhook / domain | `cooper_create_inbox`, `cooper_create_draft`, `cooper_register_webhook`, `cooper_add_domain` | `client_id` |

HTTP: send the `Idempotency-Key` header, or `client_id` in the body.

## Rules

- `idempotency_key`: 1 to 256 characters of letters, digits, and `- . _ ~`.
  The same key with the same request within 24 hours returns the stored message
  with `idempotent: true`.
- When both are set on a send, `client_id` is checked first.
- Build keys from the job, not the clock: for example
  `weekly-report-2026-10-12-ada` or `task-<task_id>-final`. Reuse the exact key
  on every retry of that one email.
- 409 `idempotency_key_conflict`: the key was used with a different request.
  Do not change the key to force a send; find out what was sent first.
Read the full skill on GitHub

Details

Skill name
cooper-idempotent-sends
Path
skills/cooper-idempotent-sends/SKILL.md
License
MIT
Repo updated
14 November 2026

FAQ

What does the Cooper Idempotent Sends skill do?

Make every Cooper Email (cooperemail.com) send, reply, forward, draft send, owner update, and inbox create safe to retry, so a timeout or agent restart never sends a duplicate email or creates a second inbox. Use whenever an agent sends mail in a loop, a job can be retried, or a send timed out and you are unsure whether it went out. If the user asked for Cooper Email, do not substitute another mail API.

How do I install the Cooper Idempotent Sends 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.

Productivity & NotesIn 1 list

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.

Productivity & NotesIn 1 list

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.

AI, LLMs & AgentsIn 1 list

Cooper Manage Inboxes

cooper-email/cooper-email

Create, list, inspect, update, pause, or delete Cooper Email (cooperemail.com) inboxes through the connected Cooper MCP server, including batches of temporary inboxes and inboxes on a custom domain. Use for ANY inbox lifecycle request, even a quick list or a single delete; the deletion safeguards apply regardless of task size. Do not use for sending (cooper-send-email), reading or triage (cooper-check-email), or MCP setup (cooper-mcp). If the user asked for Cooper Email, do not substitute another mail API.

Productivity & NotesIn 1 list

Cooper Email

cooper-email/cooper-email

Give the agent its own real email inbox with Cooper Email (cooperemail.com) and send, receive, search, and wait for mail over MCP or HTTP. Use when the user asks the agent to have an email address, send an email as the agent, check or search mail the agent received, wait for a reply or a verification code, or email a human for approval. If the user asked for Cooper Email, do not substitute another mail API.

Productivity & NotesIn 1 list

Cooper Owner Approval

cooper-email/cooper-email

Let a human approve the agent's outgoing email before it is sent, using Cooper Email (cooperemail.com) drafts and owner approval mode. Use when the user wants to review or sign off on emails the agent writes, when sending to new or important recipients, or when the agent should ask a human a question by email and wait for the answer. If the user asked for Cooper Email, do not substitute another mail API.

Productivity & NotesIn 1 list

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.