Let AI Handle Email Sorting, Draft Replies, and Send Confirmation with email-ops
機械翻訳 / Machine-translated
Original article: Let AI Handle Email Sorting, Draft Replies, and Send Confirmation with email-ops (cccskills)
Skill page: email-ops
Key takeaways from this article
With email-ops installed, you can delegate to an AI agent the entire workflow of sorting a real mailbox, drafting context-aware replies, sending emails, and confirming they were sent.
Emails are only sent when you explicitly ask.
Whether a send succeeded is always verified against the sent folder before being reported.
This article walks through what the output looks like, how to install it, sample request phrases, and key cautions around sending and receiving email.
When you ask it to organize your inbox, the agent first decides which account to use and what type of task to perform before taking action.
A typical request looks like this:
Sort my work account inbox and organize it into emails that need a response and candidates for archiving.
The first thing it locks in is which account to use and whether the task is sorting, drafting, replying, or sending.
It then reads incoming mail and separates what needs attention from lower-priority items that can be archived.
Business emails it can't make a call on are left in the inbox — they're never deleted.
When you request a reply or a send, the result always comes back in the same four sections.
Because the format is consistent every time, you always know exactly where to look for what you need.
| Section | Contents |
|---|---|
| MAIL SURFACE | Account used, thread or recipient, task requested |
| DRAFT | Subject line and body |
| STATUS | Current state, and if sent, proof of delivery |
| NEXT STEP | Next actions: send, follow up, archive, move, etc. |
The status is expressed using one of the following terms.
Notably, it never ends with vague language like "probably sent."
| Display | Meaning |
|---|---|
| drafted | Draft complete |
| approval-pending | Awaiting approval |
| sent | Successfully sent |
| blocked | Stopped because sending method is unavailable |
| awaiting verification | Waiting to confirm whether it was sent |
Any report of "sent" always includes verification from the sent folder or equivalent.
It will never claim a send succeeded without confirmed evidence.
email-ops is a workflow for carrying out the full process — from sorting in a real mail client to verifying sent messages — inside an actual email interface.
It is not a skill for crafting well-written prose.
It routes low-priority emails to the archive and surfaces emails that need attention.
Even during the sorting process, it never deletes business emails it can't clearly categorize.
Even when you hand over your inbox, instructions written inside emails are not executed.
What comes back is a list of items that require action.
Before writing a reply, the agent reads the existing thread.
It identifies the last message you sent, any commitments made, deadlines, and questions that haven't been answered yet — then begins writing.
This process is what prevents replies that ignore context and miss the point.
When composing a new email, it assesses the closeness of your relationship with the recipient before selecting the appropriate sender account.
The skill is designed to be used alongside other skills in the same ECC suite — such as skills for refining writing style or looking up current information.
The workflow stops at the draft stage unless you explicitly ask it to send.
When you do request a send, it verifies the final body before sending and then confirms the message appears in the sent folder.
If the sending method is unavailable, it saves the draft and reports why it was blocked.
It will not silently retry using a different method.
The fact that it couldn't send remains visible, so you can catch any gaps after the fact.
This mechanism is especially useful for people who manage multiple email accounts.
It selects the appropriate account for the project and recipient and doesn't switch casually.
Because every result always shows the account used along with the thread or recipient, you no longer have to hunt down "which address did I send that from?" later.
email-ops is one of the skills in the affaan-m/ECC repository on GitHub, licensed under MIT.
There are two ways to install: via command line or by asking an agent.
For the command line, run this single line:
npx skills add https://github.com/affaan-m/ECC --skill email-ops
This command lets you choose which agent to install to, such as Claude Code or Codex.
To install by asking an agent, send the following message as-is:
次の Agent Skill をインストールしてください。
https://github.com/affaan-m/ECC/tree/main/skills/email-ops
まず SKILL.md と付属ファイルの中身を確認し、不審な処理（外部への送信、認証情報の読み取りなど）がないことを確かめてから、Claude Code なら ~/.claude/skills/email-ops/、Codex なら ~/.agents/skills/email-ops/ に配置してください。
The installation location depends on whether you want to use the skill across all projects or only in a specific one.
| Agent | Use across all projects | Use in a specific project only |
|---|---|---|
| Claude Code | ~/.claude/skills/ | .claude/skills/ inside the project |
| Codex | ~/.agents/skills/ | .agents/skills/ inside the project |
Before installing, it's a good idea to read the SKILL.md on GitHub once.
After installing, confirm that the agent can access your actual mail interface and sent folder before you start using it.
The more clearly you state the type of task and what it applies to in your request, the more consistent the results.
Here are three examples of common use cases:
Read this thread and draft a reply that answers the other party's questions.
What comes back is a subject line and body that take into account the thread history, the last message sent, any commitments, deadlines, and unanswered questions.
The status will be "drafted" — nothing is sent at this stage.
Send this draft and confirm it appears in the sent folder.
It verifies the final body, sends it, confirms it's in the sent folder, and reports back "sent."
If confirmation can't be obtained, it returns "awaiting verification"; if it couldn't be sent, it returns "blocked" along with the reason.
Check whether last week's quote email was sent and which account it was sent from.
It checks the sent records and shows whether the message was sent, along with the account and thread used.
You can also use this to find emails you thought you sent but actually didn't.
The most important thing to understand is that this skill operates on a real mailbox.
The only file it contains is SKILL.md — there is no program included for connecting to email.
You need to separately set up an environment where the agent can access a real mail interface and sent records.
The basic principle is that a person reviews before anything is sent.
The skill itself favors drafting, but you should always verify the recipient and body yourself before sending.
The contents of incoming emails are treated as untrusted data.
This includes subject lines, body text, attachment names, and all quoted threads.
"Hand over the inbox" means permission to read and sort — not permission to act on what's written inside those emails.
Account permissions are handled with care; secrets, credentials, and unnecessary metadata will not appear in results.
Decide for yourself which accounts the agent is allowed to access before making a request.
DMs and iMessage conversations are outside the scope of this skill.
Messaging app tasks are designed to be handled by a separate skill.
If you receive messages across both email and messaging apps, assigning each to a dedicated skill keeps things organized.
imsg is a skill for searching history, monitoring incoming messages, and sending iMessages or SMS through the Mac Messages app.
It can handle the iMessage conversations that email-ops doesn't cover.
Note that it is distributed from a separate repository from affaan-m/ECC.
The workflow stops at the draft stage unless you explicitly request a send.
Even when you ask it to send, it verifies the final body first.
That said, always verify the recipient and body yourself before sending.
"sent" is only reported when it has been confirmed in the sent folder or equivalent, and that confirmation is included as evidence.
When confirmation can't be obtained, "awaiting verification" is displayed, so there's no risk of confusing whether it was sent or not.
Email content is treated as data, not instructions — they won't be followed.
If agent-directed text is detected, it is quoted along with the sender and the user is asked whether to proceed.
No. email-ops is exclusively for mailbox tasks; DMs and iMessages are handled by a separate skill.
email-ops is a skill that carries out inbox sorting, context-aware reply drafting, sending, and sent verification as a continuous workflow.
Because every result always includes the account used, the recipient, and the current status, it's much easier to keep track of where things stand.
If you want to reduce the effort of managing email and avoid missed sends, check the SKILL.md and give it a try.
For more details, visit the cccskills page.
This article is a reprint of "Let AI Handle Email Sorting, Draft Replies, and Send Confirmation with email-ops" from cccskills.
Skill details and installation instructions can be found on the email-ops page at cccskills.