email-ops

Manages mailbox triage, drafting, sending, and Sent-folder verification workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Mailbox work often fails silently: drafts get written without reading the thread, sends are claimed without proof, and the wrong account or channel gets used. This Skill provides an evidence-first operator workflow for real mail surfaces so every triage, draft, reply, or send ends in a verifiable state. ## Core Features & Use Cases - Evidence-first sending: Never claims a message was sent without a Sent-folder or client-side confirmation, and reports exact status words (drafted, sent, blocked, awaiting verification). - Thread-aware drafting: Reads the existing thread, identifies the last outbound touch, and surfaces commitments or unanswered questions before composing. - Account and channel discipline: Resolves the exact mailbox account, recipient, and action type before acting, and hands off DM or iMessage tasks to the appropriate workflow. - Use Case: You ask whether a proposal email to an investor was actually sent. The Skill checks the correct account's Sent folder, confirms the exact message, and reports sent status with proof rather than guessing. ## Quick Start Triage my inbox, draft a reply to the open investor thread, and confirm whether my last follow-up email was actually sent.

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?▼

Verify a sent email by checking the Sent folder or equivalent sent-copy store in the exact mailbox account used. This workflow never claims a send succeeded without that confirmation and reports status as sent, blocked, or awaiting verification.

How to draft a reply that uses the existing email thread context?▼

Read the full thread first, identify the last outbound touch, and list any commitments, deadlines, or unanswered questions before composing. This prevents contextless replies that ignore prior conversation history.

Can this handle sending from multiple email accounts?▼

Yes, the workflow resolves the exact mailbox account before acting and matches the sender to the project and recipient. It does not switch sender accounts casually and reports which account was used in the final output.

What happens when the email send surface is blocked?▼

When sending is blocked, the draft is preserved and the exact blocker is reported instead of silently switching to another transport. The status is reported as blocked with a clear next step.

When should I use email instead of DM or iMessage for outreach?▼

Use email when the task involves mailbox surfaces like threads, Sent folders, and formal correspondence. If the task is really DM or iMessage work, it should be handed off to a messages-focused workflow instead.