Email Operations

Use this skill when the actual task involves mailbox work: categorizing, drafting, replying, sending, or confirming that mail has entered the sent folder.

This is not a general writing skill, but rather an operational workflow around actual email interfaces.

Skill Stack

Invoke these native ECC skills in relevant contexts:

• brand-voice before drafting any user-facing content
• investor-outreach for emails to investors, partners, or sponsors
• customer-billing-ops when the email thread belongs to a billing/support case rather than general communication
• knowledge-ops when you need to capture a message or thread into persistent context
• research-ops when replies depend on current external facts

When to Use

• User asks to categorize an inbox or clean up low-value mail
• User needs to draft, reply to, or send a new email
• User wants to confirm whether an email was sent
• User needs to verify the account, thread, or sent record used

Safety Rails

• Draft first unless the user explicitly requests live send
• Do not claim an email was sent without confirmation from a real sent folder or client
• Do not casually switch sending accounts; select the account that matches the project and recipient
• Do not delete uncertain business mail when cleaning
• If the task is actually direct messaging or iMessage work, hand off to messages-ops

Workflow

1. Confirm the Specific Interface

Before operating, establish:

• Which email account
• Which thread or recipient
• Whether the task is categorizing, drafting, replying, or sending
• Whether the user needs only a draft or a live send

2. Read the Thread Before Writing

If replying:

• Read the existing thread
• Identify the last outbound contact
• Identify any commitments, deadlines, or unanswered questions

If creating a new outbound email:

• Establish the level of intimacy
• Select the correct channel and sending account
• Call brand-voice before drafting

3. Draft, Then Verify

For draft-only tasks:

• Generate final copy
• State the sender, recipient, subject, and purpose

For live-send tasks:

• Verify the final body first
• Send through the selected email interface
• Confirm the message has entered the sent folder or equivalent sent-copy storage

4. Report Exact Status

Use precise status language:

• Drafted
• Pending approval
• Sent
• Blocked
• Awaiting verification

If the send interface is blocked, preserve the draft and report the exact blocking reason rather than switching to a second transport method without explanation.

Output Format

Email Interface
- Account
- Email thread / recipient
- Requested action

Draft
- Subject
- Body

Status
- Drafted / Sent / Blocked
- Send proof where applicable

Next Steps
- Send
- Follow up
- Archive / move

Common Pitfalls

• Do not claim successful send without checking a sent copy
• Do not ignore thread history and write context-free replies
• Do not confuse email work with direct messaging or SMS workflows
• Do not expose secrets, auth details, or unnecessary message metadata

Verification

• Replies indicate the account and thread or recipient
• Any send claim includes sent proof or explicit client confirmation
• Final status is: Drafted / Sent / Blocked / Awaiting verification