Email Ops

This is a structured workflow for actual email operations: triage, drafting, replying, and sending with verification that messages actually landed in Sent. It enforces a draft-first default, requires reading thread history before composing replies, and won't let you claim something was sent without proof. The skill pulls in other ECC workflows when relevant (brand voice before customer-facing mail, investor outreach for sponsor threads, research ops when you need fresh facts). Built for teams that need to prove what went out and from which account, not just generate copy. The guardrails are sensible: it blocks casual account switching and won't delete uncertain business mail during cleanup.

skills.sh installs: 5.4K
GitHub stars: 300.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/ecc --skill email-ops --agent claude-code

Installs into .claude/skills of the current project.

Files

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-voice before drafting anything user-facing
investor-outreach for investor, partner, or sponsor-facing mail
customer-billing-ops when the thread is a billing/support incident rather than generic correspondence
knowledge-ops when the message or thread should be captured into durable context afterward
research-ops when a reply depends on fresh external facts