email-ops

原文涵盖的主题

• Email Ops
• Skill Stack
• When to Use
• Guardrails
• Workflow
• 1. Resolve the exact surface
• 2. Read the thread before composing
• 3. Draft, then verify

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. 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 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 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

这里只展示节选，请以完整原文和当前要求为准。