email-ops
Evidence-first mailbox triage, drafting, send verification, and sent-mail-safe follow-up workflow for ECC. Use when the user wants to organize email, draft or send through the real mail surface, or prove what landed in Sent.
Best use case
email-ops is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Evidence-first mailbox triage, drafting, send verification, and sent-mail-safe follow-up workflow for ECC. Use when the user wants to organize email, draft or send through the real mail surface, or prove what landed in Sent.
Teams using email-ops should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/email-ops/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How email-ops Compares
| Feature / Agent | email-ops | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Evidence-first mailbox triage, drafting, send verification, and sent-mail-safe follow-up workflow for ECC. Use when the user wants to organize email, draft or send through the real mail surface, or prove what landed in Sent.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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 ## 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-voice` before 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 ```text 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 / move ``` ## Pitfalls - 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
Related Skills
x-api
X/Twitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.
workspace-surface-audit
Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Gemini CLI or understanding what capabilities are actually available in their environment.
visa-doc-translate
Translate visa application documents (images) to English and create a bilingual PDF with original and translation
videodb
See, Understand, Act on video and audio. See- ingest from local files, URLs, RTSP/live feeds, or live record desktop; return realtime context and playable stream links. Understand- extract frames, build visual/semantic/temporal indexes, and search moments with timestamps and auto-clips. Act- transcode and normalize (codec, fps, resolution, aspect ratio), perform timeline edits (subtitles, text/image overlays, branding, audio overlays, dubbing, translation), generate media assets (image, audio, video), and create real time alerts for events from live streams or desktop capture.
video-editing
AI-assisted video editing workflows for cutting, structuring, and augmenting real footage. Covers the full pipeline from raw capture through FFmpeg, Remotion, ElevenLabs, fal.ai, and final polish in Descript or CapCut. Use when the user wants to edit video, cut footage, create vlogs, or build video content.
verification-loop
Comprehensive verification system for code changes
unified-notifications-ops
Operate notifications as one ECC-native workflow across GitHub, Linear, desktop alerts, hooks, and connected communication surfaces. Use when the real problem is alert routing, deduplication, escalation, or inbox collapse.
ui-demo
Record polished UI demo videos using Playwright. Use when the user asks to create a demo, walkthrough, screen recording, or tutorial video of a web application. Produces WebM videos with visible cursor, natural pacing, and professional feel.
token-budget-advisor
Offers the user an informed choice about how much response depth to consume before answering. Use this skill when the user explicitly wants to control response length, depth, or token budget. TRIGGER when: "token budget", "token count", "token usage", "token limit", "response length", "answer depth", "short version", "brief answer", "detailed answer", "exhaustive answer", "respuesta corta vs larga", "cuántos tokens", "ahorrar tokens", "responde al 50%", "dame la versión corta", "quiero controlar cuánto usas", or clear variants where the user is explicitly asking to control answer size or depth. DO NOT TRIGGER when: user has already specified a level in the current session (maintain it), the request is clearly a one-word answer, or "token" refers to auth/session/payment tokens rather than response size.
terminal-ops
Evidence-first repo execution workflow for ECC. Use when the user wants a command run, a repo checked, a CI failure debugged, or a narrow fix pushed with exact proof of what was executed and verified.
team-builder
Interactive agent picker for composing and dispatching parallel teams
tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.