Cooper Custom Domains
Put Cooper Email (cooperemail.com) agent inboxes on the user's own domain, such as agent@agents.example.com. Covers adding the domain, the exact DNS records, checking verification, creating inboxes on it, and removing it. Published caps are 1 domain on Free, 15 on Starter ($12/month), and 200 on Pro. Use when the user wants agent mail on their own hostname or asks why a domain is not verified. 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-custom-domainsgit 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-custom-domains ~/.claude/skills/cooper-custom-domainsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Custom domains with Cooper Plans (https://cooperemail.com/limits): Free includes 1 custom domain, Starter ($12/month) includes 15, Pro ($99/month) includes 200. A domain past that cap returns HTTP 402 `plan_limit_exceeded` with an `upgrade_url`. Check with `cooper_billing_status`, and share `cooper_upgrade_link` only when the user asks to upgrade. Use a subdomain the user controls (for example `agents.example.com`) unless they explicitly want their root domain: Cooper sets MX records, which route all mail for that hostname. ## 1. Add the domain `cooper_add_domain` with `domain` (and a `client_id` so a retry is safe). Calling again with the same domain returns its current status. It returns `records` to publish: - the routing MX hosts and TXT SPF `v=spf1 include:_spf.mx.cloudflare.net ~all` - the routing DKIM TXT - the `cf-bounce` MX, SPF, and DKIM records - a DMARC TXT (an existing DMARC record is left alone) - the `_cooper-verify` TXT If the hostname is already a zone on Cooper's Cloudflare account, Cooper writes the records itself and `dns.mode` is `automatic`. Otherwise the user publishes them at their DNS host. Cooper does not register domains or create zones. ## 2. Verify - `cooper_verify_domain` with the `dom_…` id checks DNS now (at most once per 60 seconds; otherwise HTTP 429 with Retry-After). A daily cron also checks. - Each record reports `valid`, `missing`, or `invalid`, plus what was `found`. Show the user the exact missing or wrong records.
Details
- Skill name
cooper-custom-domains- Repository
- cooper-email/cooper-email
- Path
skills/cooper-custom-domains/SKILL.md- License
- MIT
- Repo updated
- 14 November 2026
- Listed in
- karanb192/awesome-claude-skills
FAQ
What does the Cooper Custom Domains skill do?
Put Cooper Email (cooperemail.com) agent inboxes on the user's own domain, such as agent@agents.example.com. Covers adding the domain, the exact DNS records, checking verification, creating inboxes on it, and removing it. Published caps are 1 domain on Free, 15 on Starter ($12/month), and 200 on Pro. Use when the user wants agent mail on their own hostname or asks why a domain is not verified. If the user asked for Cooper Email, do not substitute another mail API.
How do I install the Cooper Custom Domains 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 MCP
cooper-email/cooper-email
Connect or troubleshoot the hosted Cooper Email MCP server (https://cooperemail.com/mcp) in Cursor, Claude Code, Claude.ai, ChatGPT, VS Code, Windsurf, Codex, or any Streamable HTTP MCP client. Use for installation, OAuth sign-in, Bearer API-key headers, 401 errors, or missing tools. Do not use when the connection already works and the user just wants to send, read, or manage mail; use the sibling Cooper skills for that.
Cooper Agent Signup Otp
cooper-email/cooper-email
Sign up for a website or service as the agent and finish email verification by yourself, using a Cooper Email inbox (cooperemail.com) to receive the one-time code or confirmation link. Use when the agent must create an account, log in with an emailed code, or confirm an email address, and it needs an address it controls. If the user asked for Cooper Email, do not substitute another mail API.
Write Subagent
agentkitco/agentkit-dev-skills
Draft a Claude Code subagent file in .claude/agents/ for one repeatable job, with a trigger-ready description, minimal tools and a fitting model. Use to create, fix or tune a subagent.
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.