/skill

Email Ops

Created by ECC. Original work and credit belong to ECC.

Use this skill for real mailbox work. It can sort mail, write a draft, reply, send mail, or prove that mail reached the Sent folder.

Do not use it only to write sample email text. This skill works with a real mail account.

Other Skills

Use these ECC skills when they fit:

• Use brand-voice before writing mail for the user.
• Use investor-outreach for investors, partners, or sponsors.
• Use customer-billing-ops for bills, refunds, or support cases.
• Use knowledge-ops when key facts from the thread should be saved.
• Use research-ops when the reply needs new facts.
• Use messages-ops for a text message, DM, or iMessage.

If a needed skill is not present, say so. Then do the safe parts of the task.

When to Use

Use this skill when the user asks to:

• Sort, label, move, or archive inbox mail.
• Find mail that needs a reply.
• Write a new email or reply.
• Send an email from a real account.
• Check if an email was sent.
• Show which account, thread, or Sent item was used.
• Follow up on mail that was sent before.

Safety Rules

• Make a draft first unless the user clearly asks you to send.
• Never send when the user only asks for a draft.
• Never say mail was sent until you find it in Sent or get a clear success note from the mail app.
• Use the account that fits the project and the person.
• Ask before changing the sender account if the right account is not clear.
• Check the To, Cc, Bcc, subject, body, and files before sending.
• Do not add a person to Cc or Bcc unless the user asks or the thread makes it clear.
• Do not open or send files that seem unsafe or do not match the task.
• Do not delete mail unless the user clearly asks. Archive or move mail when cleanup is needed.
• Do not archive mail with an open task, due date, bill, legal issue, or unclear business need.
• Do not send the same mail twice. Check the thread and Sent folder first.
• Do not expose passwords, login data, private links, or extra mail details.
• Do not use a DM or text app as a backup without telling the user.

Workflow

1. Pick the Exact Mail

Before acting, find:

• The mailbox account.
• The thread or person.
• The task: sort, draft, reply, send, check, or follow up.
• Whether the user wants a draft or a live send.

If one of these facts is not clear, ask before any send, delete, or large mailbox change.

2. Read Before You Write

For a reply:

• Read the full thread.
• Find the last message from each side.
• Check if a reply was already sent.
• List open questions.
• Note promises, dates, prices, files, and next steps.
• Keep the same subject and thread unless there is a good reason not to.

For a new email:

• Check how well the user knows the person.
• Pick the right sender account.
• Use brand-voice if it is present.
• Make the goal and request clear.

3. Sort Mail Safely

For inbox cleanup:

• Group mail by clear type, such as urgent, reply needed, read later, receipt, or junk.
• Keep mail with open work or unclear value.
• Archive only mail that is safe to remove from the inbox.
• Show the planned changes before a large batch.
• Report how many items were moved, archived, or left alone.

4. Make and Check the Draft

Before a live send, check:

• Sender account.
• To, Cc, and Bcc.
• Subject.
• Final body.
• Names, dates, links, and money.
• Files and file names.
• Any promise or due date.
• Whether the same message was already sent.

For draft-only work, give the final copy and say who it is for.

5. Send and Prove It

For a live send:

1. Send through the chosen mail app.
2. Look for the new item in Sent.
3. Match the sender, recipient, subject, and send time.
4. If possible, also match the thread or message ID.
5. Report only what the proof shows.

A success pop-up alone may not prove the send. If Sent cannot be checked, use the status awaiting verification.

If the send fails:

• Keep the draft.
• Do not try another account or app without approval.
• Report the exact error in safe terms.
• Use the status blocked.

6. Follow Up Safely

Before sending a follow-up:

• Check the thread for a new reply.
• Check Sent to find the last send date.
• Make sure the wait time fits the case.
• Do not follow up if the person already answered.
• Keep the note short and state the next step.

Status Words

Use one of these exact terms:

• drafted: The email is ready but not sent.
• approval-pending: The draft needs user approval.
• sent: The email was sent and proof was found.
• blocked: The work could not be done.
• awaiting verification: The app says it sent, but Sent proof is not yet found.

Output Format

MAIL SURFACE
- Account:
- Thread or recipient:
- Requested action:

DRAFT
- To:
- Cc:
- Bcc:
- Subject:
- Body:
- Files:

STATUS
- State:
- Sent proof:
- Blocker:

NEXT STEP
- Action:

Leave out fields that do not apply. Never place secret data in this report.

Example

User request:

Reply to Maya from my work account. Tell her Friday works. Draft only.

Result:

MAIL SURFACE
- Account: Work account
- Thread or recipient: Maya Chen
- Requested action: Reply, draft only

DRAFT
- To: Maya Chen
- Subject: Re: Project review
- Body:

Hi Maya,

Friday works for me. Please send the time that works best for you.

Thanks,
Luke

STATUS
- State: drafted
- Sent proof: Not needed. The user asked for a draft only.

NEXT STEP
- Action: Review and send after approval.

Edge Cases

• If two people have the same name, match the email address and thread before acting.
• If more than one account could be right, do not guess before sending.
• If the thread is missing, say what you searched and ask for more detail.
• If the user asks to send a blank, unclear, or harmful message, stop and ask what they want changed.
• If a file is missing, do not send unless the user says to send without it.
• If a link looks wrong or unsafe, do not open or send it.
• If the mail app shows a send error, do not mark the message as sent.
• If the message is in Outbox but not Sent, use awaiting verification.
• If Sent has two matching items, report the possible duplicate.
• If a reply came in while drafting, read it and update the draft before sending.
• If many messages will be changed, show the rule and count before making the change.

Final Check

Before finishing, make sure:

• The account is named.
• The thread or recipient is named.
• The requested action is clear.
• The status uses an exact status word.
• Every sent claim has Sent proof.
• A blocked send keeps the draft.
• No secret or unneeded private data is shown.