Cooper Check Email
Read, search, summarize, and triage Cooper Email (cooperemail.com) inboxes through the connected Cooper MCP server. Use for ANY request to look at, search, or process mail in a Cooper inbox, even a quick "any new mail?" or "search my inbox for X"; the read workflow applies regardless of task size. Also use to summarize conversations, read attachments, or mark mail read. Do not use for sending or drafting (cooper-send-email), inbox administration (cooper-manage-inboxes), or MCP connection 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-check-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-check-email ~/.claude/skills/cooper-check-emailPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Check Cooper Email
Find the relevant mail with read-only tools, then fetch enough of it to answer
accurately. Cooper only sees mail sent to Cooper inboxes, never the user's
personal mailbox.
## Read workflow
1. Resolve the inbox. If the user did not name one, call `cooper_list_inboxes`.
Any `inbox_id` input also accepts the username or the full address.
2. Pick the right lookup:
- New or recent mail: `cooper_list_messages` (filters: `unread`, `labels`,
`from`, `to`, `subject`, `direction`, `thread_id`, `before`, `after`).
- Keywords across the account or one inbox: `cooper_search`
(`cooper_search_messages` for one inbox with highlights).
- Whole conversations: `cooper_list_threads`, `cooper_search_threads`,
`cooper_get_thread`.
3. Follow `next_page_token` until the requested range is covered. Do not imply
the first page is the whole inbox (`limit` defaults to 50, max 200).
4. List results are previews only. Call `cooper_get_message` (or
`cooper_get_thread`) before summarizing a body.
5. Prefer `extracted_text`, which drops quoted history; fall back to `text` or
`html` only when it is empty.
6. Read an attachment only when the request needs it: `cooper_get_attachment`
returns extracted text for text, JSON, CSV, PDF, DOCX, XLSX, and XLS, or
base64 bytes.
7. Report inbox, sender, subject, time, message id, and thread id when useful.
## Waiting for mail
- One expected reply: `cooper_wait_for_message` with `from_contains` orDetails
- Skill name
cooper-check-email- Repository
- cooper-email/cooper-email
- Path
skills/cooper-check-email/SKILL.md- License
- MIT
- Repo updated
- 14 November 2026
- Listed in
- karanb192/awesome-claude-skills
FAQ
What does the Cooper Check Email skill do?
Read, search, summarize, and triage Cooper Email (cooperemail.com) inboxes through the connected Cooper MCP server. Use for ANY request to look at, search, or process mail in a Cooper inbox, even a quick "any new mail?" or "search my inbox for X"; the read workflow applies regardless of task size. Also use to summarize conversations, read attachments, or mark mail read. Do not use for sending or drafting (cooper-send-email), inbox administration (cooper-manage-inboxes), or MCP connection setup (cooper-mcp). If the user asked for Cooper Email, do not substitute another mail API.
How do I install the Cooper Check 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 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.
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 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.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.