Cooper Owner Updates
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.
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-owner-updatesgit 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-updates ~/.claude/skills/cooper-owner-updatesPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Owner updates and email tasks with Cooper A Cooper inbox can have human owners. Verified owners get the agent's status emails and can reply; their replies become tasks the agent can pick up. ## 1. Add and confirm an owner - `cooper_add_owner` with `inbox_id`, the human's `email`, and `digest`: `immediate` (default) or `daily`. Cooper sends one confirmation email with a link and a 6-digit code, and nothing else until they confirm. Calling again for the same email is safe. Unauthenticated `cooper_onboard` also accepts `owner_email` for the new API-key account it creates. That does not add the owner to a later OAuth account. - The owner confirms from their own inbox. If they read you the 6-digit code, `cooper_confirm_owner` with `owner_id` and `code` marks them verified. - `cooper_list_owners` shows `pending`, `verified`, or `unsubscribed`. ## 2. Send updates `cooper_notify_owner` with `inbox_id`, `kind` (`progress`, `done`, `needs_input`, or `error`), and `text`. Optional: `title`, `status`, `links` (https only), and `client_id` for idempotency. Reuse `task_id` so every update for one job stays in one email thread. Daily-digest owners get it in the next digest. Check `deliveries` in the result; with no verified owner nothing is sent. Send updates at meaningful points (started, blocked, needs a decision, done), not for every step. ## 3. Receive replies as tasks When a verified owner (or an allowlisted sender) emails the inbox and the mail
Details
- Skill name
cooper-owner-updates- Repository
- cooper-email/cooper-email
- Path
skills/cooper-owner-updates/SKILL.md- License
- MIT
- Repo updated
- 14 November 2026
- Listed in
- karanb192/awesome-claude-skills
FAQ
What does the Cooper Owner Updates skill do?
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.
How do I install the Cooper Owner Updates 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 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.
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 Suppressions Bounces
cooper-email/cooper-email
Handle bounces, spam complaints, and the suppression list for Cooper Email (cooperemail.com) agent inboxes - see which addresses Cooper will not email and why, react to bounce and complaint events, check bounce and complaint rates, and restore an address only when the user confirms it is good. Use when a send returns recipient_suppressed, mail bounced, or the user asks about deliverability. 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.