Cooper Manage Inboxes
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.
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-manage-inboxesgit 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-manage-inboxes ~/.claude/skills/cooper-manage-inboxesPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Manage Cooper inboxes Keep the user's intended address, scope, and data intact. ## Discover - `cooper_whoami`: which account and key this connection uses, and whether the key is limited to one inbox or a permission list. - `cooper_list_inboxes` to find inboxes; `cooper_get_inbox` for one inbox's address, display name, metadata, status, screening, and `send_mode`. - `cooper_billing_status` for plan limits (inboxes, monthly sends, custom domains). ## Create - OAuth client (Cursor plugin, Claude, ChatGPT, Grok Bot) with no session yet: finish OAuth first. Do not call `cooper_onboard` on that connector. Unauthenticated `cooper_onboard` returns a one-time API key for a different account and does not sign the connector in. - Signed in, or a saved Bearer key: `cooper_create_inbox` with the requested `username`, `display_name`, `metadata`, and a stable `client_id` so a retry returns the same inbox instead of creating another. - Check a name first with `check_username: true` (no inbox is created). - Several or temporary addresses: `cooper_create_inboxes` with `count`, an optional `prefix`, `labels`, and `ttl_hours` or `expires_at`. Expired inboxes are deleted by the daily cron and stop counting toward the plan. - Custom domain: pass `domain` only when it belongs to this account, is verified, and has `mail.receiving` true (see `cooper_list_domains`). Adding a domain is `cooper_add_domain`. Published caps (https://cooperemail.com/limits):
Details
- Skill name
cooper-manage-inboxes- Repository
- cooper-email/cooper-email
- Path
skills/cooper-manage-inboxes/SKILL.md- License
- MIT
- Repo updated
- 14 November 2026
- Listed in
- karanb192/awesome-claude-skills
FAQ
What does the Cooper Manage Inboxes skill do?
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.
How do I install the Cooper Manage Inboxes 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 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.
Cooper Idempotent Sends
cooper-email/cooper-email
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.
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.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.