email-ops
by affaan-memail-ops is an evidence-first mailbox workflow skill for triage, drafting, replying, sending, and Sent verification. Use it when you need safe email handling, the right sender account, and proof of what was actually sent. It is ideal for operational inbox work, not just polished writing.
This skill scores 78/100, which means it is a solid directory candidate: users should expect a genuinely useful email-operations workflow with enough specificity to reduce guesswork, though it is not yet backed by supporting scripts or reference files. The skill is clear about when to use it, what it covers, and the need for sent-folder verification, so it should be easy for agents to trigger correctly for mailbox triage, drafting, sending, and proof of delivery.
- Explicit trigger guidance for inbox triage, drafting, sending, and proving a message landed in Sent
- Operational guardrails are concrete, including draft-first behavior and no claims of sending without Sent-folder or client-side confirmation
- Workflow is more than generic writing help: it frames email as an actual mail-surface operation and points to related ECC-native skills when relevant
- No install command, scripts, or reference files, so adoption still depends on reading the SKILL.md carefully
- Limited evidence of deeper task-specific procedures beyond the core workflow, so complex mailbox edge cases may still require manual judgment
Overview of email-ops skill
What email-ops is for
email-ops is an email-ops skill for real mailbox work: triage, drafting, replying, sending, and verifying what actually landed in Sent. It is best for people who need operational confidence, not just polished prose.
Who should install it
Use email-ops if you handle active inboxes, run outbound follow-up, or need evidence that a message was sent from the correct account. It is a strong fit when the main job is to move mail safely and document what happened.
What makes it different
This skill is not a generic email-ops for Email Writing prompt. It emphasizes workflow discipline: draft first, confirm account choice, avoid risky cleanup, and verify sent state before claiming completion. That makes it useful when mistakes have business cost.
How to Use email-ops skill
Install and first files to read
For email-ops install, add the skill from the repo path and start with the core instructions: SKILL.md first, then any linked context files if they exist. In this repo, SKILL.md is the main source of truth, so there is little hidden machinery to hunt for.
Turn a rough request into a usable prompt
A strong email-ops usage prompt states the mail task, the account, the recipient or thread, and the required level of proof. Example: “Use email-ops to draft a reply for the ACME thread from the support account; do not send yet; preserve tone; tell me what account and Sent evidence I should check.” That gives the skill enough context to operate safely.
Workflow that produces better output
Use the email-ops guide pattern: identify whether this is triage, draft, reply, send, or sent verification; choose the correct sender account; and only then prepare the message. If the task includes cleanup, keep uncertain business mail intact until the thread is understood.
Practical inputs that matter most
For email-ops, the highest-value inputs are the target thread, the intended sender identity, the purpose of the mail, and any “must not do” constraints such as “draft only” or “do not mention pricing.” If the reply depends on current facts, pair it with research before writing.
email-ops skill FAQ
Is email-ops only for writing emails?
No. The email-ops skill is equally about inbox triage, send discipline, and proof of delivery state. That is why it is more reliable than a plain writing prompt when the mailbox itself matters.
When should I not use email-ops?
Do not use it for casual text-message style communication, and do not use it when the job is only to produce generic copy with no mail workflow. If you only need a sentence rewritten, a simpler prompt is enough.
Does it work for beginners?
Yes, if you can state who the message is for, which account should send it, and whether sending is allowed. Beginners usually get the best results by asking for a draft first and reviewing account/sent-status guidance before taking action.
How is it different from ordinary prompts?
Ordinary prompts focus on wording. email-ops focuses on execution safety: correct mailbox, correct send decision, and verifiable results. That matters when you need to know what was actually sent, not just what was written.
How to Improve email-ops skill
Give the skill fewer ambiguities
The biggest quality gain comes from naming the thread, sender, recipient, desired outcome, and risk level up front. “Reply to the latest billing email from the finance account and keep it noncommittal” is far more useful than “respond to this.”
Ask for proof-oriented checks
If you need email-ops to help with send verification, ask for the exact evidence you want: Sent folder match, account used, timestamp, or thread subject. That reduces the chance of a vague “done” when you actually need auditability.
Iterate after the first draft
Use the first pass to catch tone, account choice, and missing facts. Then refine with concrete edits such as “shorter,” “more direct,” “do not promise a timeline,” or “include only the next-step question.” The skill is strongest when you tighten scope between iterations.
Watch for common failure modes
The main failure modes are accidental sender confusion, over-cleaning an inbox, and treating unsent drafts like completed sends. If you avoid those, email-ops is most useful as a disciplined operator layer for email work rather than a generic composition tool.