Cooper Owner Approval

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.

Productivity & Notes Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add cooper-email/cooper-email

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add cooper-email/cooper-email --skill cooper-owner-approval
Manual install
git 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-owner-approval ~/.claude/skills/cooper-owner-approval

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Owner approval for agent email with Cooper Email

Real email cannot be recalled. With Cooper, a human owner can approve each send
from their own email client, and the agent can draft first and ask.

Assumes a Cooper inbox and key (`COOPER_API_KEY`, inbox id `$INBOX`). No inbox
yet on HTTP? `POST https://cooperemail.com/api/v1/onboard` with `{"username":"<slug>","owner_email":"<human>"}`,
then send the returned key as `Authorization: Bearer`. On an OAuth client,
finish sign-in first and call `cooper_create_inbox`. `cooper_onboard` does not
attach its key to that OAuth session. Details: https://cooperemail.com/AGENTS.md

## 1. Add and verify a human owner

```bash
curl -s https://cooperemail.com/api/v1/inboxes/$INBOX/owners \
  -H "Authorization: Bearer $COOPER_API_KEY" -H 'content-type: application/json' \
  -d '{"email":"owner@example.com"}'
```

MCP: `cooper_add_owner`. Cooper emails the owner a confirmation link and a
6-digit code. Nothing else is sent to them until they confirm. Ask the human to
confirm from their own inbox. You cannot confirm for them: an API key cannot
submit owner links. `cooper_list_owners` shows when they are verified.

## 2. Turn on approval mode

```bash
curl -s -X PATCH https://cooperemail.com/api/v1/inboxes/$INBOX \
  -H "Authorization: Bearer $COOPER_API_KEY" -H 'content-type: application/json' \
  -d '{"send_mode":"approval"}'
```

MCP: `cooper_update_inbox` with `send_mode: "approval"`.
Read the full skill on GitHub

Details

Skill name
cooper-owner-approval
Path
skills/cooper-owner-approval/SKILL.md
License
MIT
Repo updated
14 November 2026

FAQ

What does the Cooper Owner Approval skill do?

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.

How do I install the Cooper Owner Approval 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.

Productivity & NotesIn 1 list

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.

Productivity & NotesIn 1 list

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.

AI, LLMs & AgentsIn 1 list

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.

Productivity & NotesIn 1 list

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.

Productivity & NotesIn 1 list

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.

Productivity & NotesIn 1 list

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.