Email Ops

This is a structured workflow for handling real email through Claude, not just writing drafts in isolation. It enforces evidence-first behavior: you don't claim a message was sent without checking the Sent folder, you read the thread before replying, and you explicitly verify which account and recipient you're targeting. It's designed for the ECC environment and pulls in other skills like brand voice or investor outreach when the context demands it. The workflow splits draft-only from live-send clearly, and the output format forces you to report exact state with proof. If you're doing actual mailbox operations where mistakes have consequences, the guardrails here prevent the usual LLM habit of confabulating send confirmations.

skills.sh installs: 3.5K
GitHub stars: 229.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/everything-claude-code --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