email-ops

Triage mailboxes, compose drafts, send messages, and verify sent-copy presence.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Maelwalser/claude-config --skill email-ops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: email-ops
Source: https://github.com/Maelwalser/claude-config/tree/main/skills/email-ops
Command: npx skills add https://github.com/Maelwalser/claude-config --skill email-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined, evidence-first workflow for mailbox triage, composing drafts, performing live sends, and verifying that messages landed in Sent. It prevents accidental or unverifiable sends, preserves thread context, and ensures accurate reporting of message state for operational and business use.

Core Features & Use Cases

  • Inbox triage: identify low-signal mail to archive, surface important threads, and resolve backlog safely.
  • Drafting and reply composition: produce context-aware drafts that respect brand voice and thread history before any live send.
  • Send verification: confirm the presence of a sent-copy or equivalent client-side confirmation before asserting that a message was sent.
  • Use case: prepare an investor reply, confirm the correct sender account, draft in the project's voice, and verify the message appears in Sent before reporting "sent".

Quick Start

Triage the '[email protected]' mailbox for threads from '[email protected]', draft a reply in the brand voice, and verify the sent-copy in Sent before reporting status.

Frequently Asked Questions about email-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify an email was actually sent before reporting delivery status?

To verify an email was actually sent, you must confirm the presence of a sent-copy in the Sent folder or obtain equivalent client-side confirmation before asserting delivery. This sent-proof step ensures accurate operational reporting.

What is the best way to triage a mailbox backlog and identify low-signal emails?

The best way to triage a mailbox backlog is to apply an evidence-first workflow that identifies low-signal mail to archive while surfacing important threads. This safely resolves inbox clutter by evaluating thread history across specified mail accounts.

Can I draft email replies that automatically respect existing thread history and brand voice?

Yes, you can draft email replies that respect brand voice and thread history. The drafting process produces context-aware drafts by evaluating the named mail surface and thread history before staging any live send.

How do I prevent accidental or unverifiable email sends when composing operational messages?

To prevent accidental or unverifiable email sends, you must stage drafts and require a sent-folder or client-side confirmation step before declaring delivery. This disciplined workflow preserves thread context and prevents unverified send actions.

Does email triage and verified sending work without direct access to the mail surface?

No, email triage and verified sending requires access to the named mail surface and thread history. You also need the ability to compose and stage drafts within the specified mail accounts to execute the workflow accurately.