messages-ops

Topics in the source

• Messages Ops
• Skill Stack
• When to Use
• Guardrails
• Workflow
• 1. Resolve the exact thread
• 2. Read before drafting
• 3. Handle codes as a focused retrieval task

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. 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 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 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 Before doing anything else, settle: message surface sender / recipient / service time window whether the task is r

This is an excerpt. Refer to the complete source and its current requirements.