cooper-manage-inboxes Skill
通过已连接的 Cooper MCP 服务器创建、列出、查看、更新、暂停或删除 Cooper Email(cooperemail.com)收件箱,包括批量临时收件箱和自定义域名收件箱。任何收件箱生命周期相关请求都必须使用,哪怕只是快速列一下或删一个;删除保护机制不因任务大小而豁免。不要用于发送(cooper-send-email)、阅读或分拣(cooper-check-email),也不要用于 MCP 配置(cooper-mcp)。如果用户指定了 Cooper Email,不要换成其他邮件 API。
安装方式:把技能目录放入 ~/.claude/skills/(Claude Code)或在 claude.ai 设置中启用;也可复制右侧安装命令一键添加。
技能指令原文(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_inboxesto find inboxes;cooper_get_inboxfor one inbox's
address, display name, metadata, status, screening, and send_mode.
cooper_billing_statusfor 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_inboxwith the requestedusername,
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_inboxeswithcount, 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
domainonly 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):
Free includes 1 custom domain, Starter 15, Pro 200. The next domain past
the cap returns HTTP 402. Publish the returned DNS records and check with
cooper_verify_domain.
Never invent a domain or assume it is verified.
- HTTP 409
inbox_exists: the name is taken, pick another. HTTP 402: plan
limit; tell the user and share cooper_upgrade_link only if they ask.
Update
cooper_update_inbox changes display_name, metadata (keys merge; a null
value removes a key), screening (off, observe, hold), status (paused stops
sending and new mail without deleting anything; active resumes), and
send_mode (direct or approval; see cooper-owner-approval).
Delete
cooper_delete_inbox deletes the inbox and its messages. Only call it after
showing the exact inbox id and address and getting explicit confirmation. If
the user only wants it to stop, offer status: "paused" instead. An inbox in
approval mode returns HTTP 202 and is deleted only after a verified owner
confirms the emailed link. cooper_delete_thread removes one conversation;
confirm it the same way.
Guardrails
- Create or delete only what the user asked for. A changed target invalidates
an earlier confirmation.
- Do not broaden an inbox-scoped key; new keys are minted over HTTP
(POST /api/v1/keys) so the secret stays out of the chat.
- Sub-accounts with their own key and inbox quota:
cooper_create_workspace,
cooper_list_workspaces, cooper_update_workspace, cooper_delete_workspace.
- Never expose API keys or unrelated mail in the result.