AGENT SKILLBY AFFAAN-M
Email ops
AT A GLANCE
Email ops is an email skill for AI agents. Evidence-first mailbox triage, drafting, send verification, and sent-mail-safe follow-up workflow for ECC. The affaan-m/ecc repository on GitHub, maintained by affaan-m, has 243K stars and the MIT license. To add it, run npx skills add affaan-m/ecc --skill email-ops
- SOURCE REPOSITORY
- affaan-m/ecc (opens GitHub in a new tab)
- REPO STARS
- SOURCE REPOSITORY
- LICENSE
- MIT
- CATEGORIES
- SKILL.MD SIZE
- 3.1 KB116 LINES
QUICK ANSWER
- WHAT IT IS01
- Evidence-first mailbox triage, drafting, send verification, and sent-mail-safe follow-up workflow for ECC. Its edge is a particular angle on email marketing, giving the agent tighter constraints than a plain email ops request.
- INPUTS02
- Context for email marketing: your goals, audience, constraints, and any source material the skill asks for.
- OUTPUT03
- A ready-to-use result for email marketing: the analysis, copy, or recommendations the agent produces.
INSTALL
One command adds this skill from its source repository.
npx skills add affaan-m/ecc --skill email-opsREAD THE SKILL.MD BELOW BEFORE YOU RUN IT. SKILLS INSTRUCT YOUR AGENT.
SKILL.MD
The full file, as published in the source repository. Copy it, download it or open it on GitHub.
ON THIS PAGE · 11
Email Ops#
Use this when the real task is mailbox work: triage, drafting, replying, sending, or proving a message landed in Sent.
This is not a generic writing skill. It is an operator workflow around the actual mail surface.
Skill Stack#
Pull these ECC-native skills into the workflow when relevant:
brand-voicebefore drafting anything user-facinginvestor-outreachfor investor, partner, or sponsor-facing mailcustomer-billing-opswhen the thread is a billing/support incident rather than generic correspondenceknowledge-opswhen the message or thread should be captured into durable context afterwardresearch-opswhen a reply depends on fresh external facts
When to Use#
- user asks to triage inbox or archive low-signal mail
- user wants a draft, reply, or new outbound email
- user wants to know whether a mail was already sent
- the user wants proof of which account, thread, or Sent entry was used
Guardrails#
- draft first unless the user clearly asked for a live send
- never claim a message was sent without a real Sent-folder or client-side confirmation
- do not switch sender accounts casually; choose the account that matches the project and recipient
- do not delete uncertain business mail during cleanup
- if the task is really DM or iMessage work, hand off to
messages-ops
Workflow#
1. Resolve the exact surface#
Before acting, settle:
- which mailbox account
- which thread or recipient
- whether the task is triage, draft, reply, or send
- whether the user wants draft-only or live send
2. Read the thread before composing#
If replying:
- read the existing thread
- identify the last outbound touch
- identify any commitments, deadlines, or unanswered questions
If creating a new outbound:
- identify warmth level
- select the correct channel and sender account
- pull
brand-voicebefore drafting
3. Draft, then verify#
For draft-only work:
- produce the final copy
- state sender, recipient, subject, and purpose
For live-send work:
- verify the exact final body first
- send through the chosen mail surface
- confirm the message landed in Sent or the equivalent sent-copy store
4. Report exact state#
Use exact status words:
- drafted
- approval-pending
- sent
- blocked
- awaiting verification
If the send surface is blocked, preserve the draft and report the exact blocker instead of improvising a second transport without saying so.
Output Format#
MAIL SURFACE
- account
- thread / recipient
- requested action
DRAFT
- subject
- body
STATUS
- drafted / sent / blocked
- proof of Sent when applicable
NEXT STEP
- send
- follow up
- archive / movePitfalls#
- do not claim send success without a sent-copy check
- do not ignore the thread history and write a contextless reply
- do not mix mailbox work with DM or text-message workflows
- do not expose secrets, auth details, or unnecessary message metadata
Verification#
- the response names the account and thread or recipient
- any send claim includes Sent proof or an explicit client-side confirmation
- the final state is one of drafted / sent / blocked / awaiting verification
FAQ
07 QUESTIONS
01What is the Email ops agent skill?
Evidence-first mailbox triage, drafting, send verification, and sent-mail-safe follow-up workflow for ECC. It is listed under email in the 100xLab agent skills directory.
02How do I install Email ops in Cursor, Claude Code, or Codex?
Run npx skills add affaan-m/ecc --skill email-ops in the project where you want it, then ask your agent for the skill by name. The --skill flag installs only Email ops, not every skill in the repository.
03What does the Email ops SKILL.md cover?
The SKILL.md includes sections on Skill Stack, When to Use, Guardrails, Workflow, Resolve the exact surface and Read the thread before composing. Read the full text on this page or in plain markdown at /resources/agent-skills/affaan-m-ecc--email-ops--k9iaeh/raw.
04Which agents can use Email ops?
Email ops installs with the cross-agent skills installer (npx skills add), which sets it up for agents such as Claude Code, Cursor and Codex. Each agent loads the SKILL.md when you ask for the skill by name.
05What license is Email ops under?
The affaan-m/ecc repository declares the MIT license. Read the license file in the repository before you copy or redistribute the skill.
06Is Email ops free to use?
Reading, copying and installing Email ops costs nothing: it is published in a public GitHub repository under the MIT license. Reuse and redistribution follow that license.
07Where is the source of Email ops?
Email ops comes from https://github.com/affaan-m/ecc, which has 243K GitHub stars. The SKILL.md is at https://github.com/affaan-m/ecc/blob/HEAD/skills/email-ops/SKILL.md. The author is affaan-m.
Need an agent workflow built around your stack?
Tell us the workflow you want automated. We reply within 4 working hours (IST).
ATTRIBUTION
Email ops was written by its original authors and is published in affaan-m/ecc (opens GitHub in a new tab) under the MIT license. All rights stay with the original authors.
100xLab did not write, maintain or endorse this skill. This page lists it for discovery. Repo stars belong to the source repository, not to the skill. Review any skill before you install it.