Cooper Suppressions Bounces
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.
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-suppressions-bouncesgit 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-suppressions-bounces ~/.claude/skills/cooper-suppressions-bouncesPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Suppressions and bounces with Cooper Cooper protects the sender's reputation automatically: after a permanent bounce or a complaint, the address goes on the account's suppression list, and later sends to it return HTTP 403 `recipient_suppressed`. Nothing is sent, stored, or counted against the plan. ## See what happened - `cooper_list_suppressions`: every suppressed address with `reason` (`bounce`, `complaint`, or `manual`), the `source_message_id` that caused it, and when. An inbox-scoped key gets 403 `permission_denied`; use an account-level key or OAuth. - `cooper_get_message` on the source message shows what was sent. - `cooper_list_events` with `types: "message.bounced,message.complained"`, or a webhook on those events (`cooper-webhooks`), tells you as it happens. - `cooper_get_metrics` with `kind: "rates"` returns sent, bounced, complained, `bounce_rate`, and `complaint_rate` (default last 30 days). ## What to do - Bounce: tell the user the address failed and ask for a corrected one. Do not retry the same address. - Complaint: the recipient marked the mail as spam. Stop mailing them and tell the user. - Restore an address with `cooper_delete_suppression` only when the user confirms it is valid and the person wants the mail (for example a typo was fixed or a full mailbox was cleared). - Rising rates: slow down, check the recipient list, and consider an allow list (`cooper_create_list_entry`, direction `send`, type `allow`) or owner
Details
- Skill name
cooper-suppressions-bounces- Repository
- cooper-email/cooper-email
- Path
skills/cooper-suppressions-bounces/SKILL.md- License
- MIT
- Repo updated
- 14 November 2026
- Listed in
- karanb192/awesome-claude-skills
FAQ
What does the Cooper Suppressions Bounces skill do?
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.
How do I install the Cooper Suppressions Bounces 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 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.
Cooper Send Email
cooper-email/cooper-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.
Human in the Loop
cooper-email/cooper-email
Keep a human owner in the loop by email with Cooper Email. Use when the user wants progress updates, approval requests, or questions sent to them by email during a long task, and wants to answer by replying.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.