messages-ops

# Messages Ops Use this when the task is live-message retrieval: iMessage, DMs, recent one-time codes, or thread inspection before a follow-up. This is not email work. If the dominant surface is a mailbox, use `email-ops`. ## Skill Stack Pull these ECC-native skills into the workflow when relevant: - `email-ops` when the message task is really mailbox work - `connections-optimizer` when the DM thread belongs to outbound network work - `lead-intelligence` when the live thread should inform targeting or warm-path outreach - `knowledge-ops` when the thread contents need to be captured into durable context ## When to Use - user says "read my messages", "check texts", "look in DMs", or "find the code" - the task depends on a live thread or a recent code delivered to a local messaging surface - the user wants proof of which source or thread was inspected ## Guardrails - resolve the source first: - local messages - X / social DM - another browser-gated message surface - do not claim a thread was checked without naming the source - do not improvise raw database access if a checked helper or standard path exists - if auth or MFA blocks the surface, report the exact blocker ## Workflow ### 1. Resolve the exact thread Before doing anything else, settle: - message surface - sender / recipient / service - time window - whether the task is retrieval, inspection, or prep for a reply ### 2. Read before drafting If the task may turn into an outbound follow-up: - read the...