Retrieve messages from iMessage or social DMs, find recent one-time codes, and inspect conversations before preparing replies. The workflow identifies the source, sender, and time window, then reports what was found or the specific access blocker.
Evidence-first live messaging workflow for ECC. Use when the user wants to read texts or DMs, recover a recent one-time code, inspect a thread before replying, or prove which message source was actually checked.
messages-ops provides a structured process for checking messages in iMessage and social DMs. It first narrows down the service, sender or thread, and time window, then summarizes message content or retrieves a recently received one-time code. Results name the source and period checked and state whether reading finished, a code was found, or access was blocked.
Use it when you want to check recent messages or find an authentication code. It also helps you review the latest incoming messages and unresolved topics before preparing a reply. When you need to know which sources were actually inspected, the report makes that explicit.
Access to the relevant service is required. If authentication or MFA, meaning multifactor authentication, blocks access, the skill reports the specific cause. Mailbox-focused tasks belong to email-ops. Sending replies is not its main task; when needed, it hands the work to an appropriate sending skill.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 19, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
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 workconnections-optimizer when the DM thread belongs to outbound network worklead-intelligence when the live thread should inform targeting or warm-path outreachknowledge-ops when the thread contents need to be captured into durable contextBefore doing anything else, settle:
If the task may turn into an outbound follow-up:
For one-time codes:
Return:
SOURCE
- message surface
- sender / thread / service
RESULT
- message summary or code
- time window
STATUS
- read / code-found / blocked / awaiting reply draft
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Design and audit interfaces for Web, iOS, and Android using WCAG 2.2 accessibility guidance. Check screen-reader labels, keyboard navigation, contrast, and control sizes to identify barriers and guide implementation for people using assistive technology.
Investigate unreliable AI agents across 12 layers, including instructions, memory, tool execution, and display. Use code and logs to trace failures, rank findings by severity, and produce an ordered repair plan that prioritizes code changes.
Compare coding agents on tasks from your own codebase. Define success checks, run agents in separate Git working directories, and report pass rates, available API costs, completion time, and consistency across repeated trials.
Design and refine an AI agent’s available actions, tool inputs, and result formats. Define recovery steps for errors, manage the information kept in context, and evaluate changes through completion rates, retries, and cost per successful task.
Diagnose AI agent runs that fail repeatedly, loop through tools, or lose track of the task. Capture errors and environment details, test a focused recovery action, and produce a report explaining the evidence and outcome.
Diagnose failed AI agent runs by capturing errors, checking likely causes, and choosing small, reversible recovery actions. The workflow produces a structured report of the failure, recovery steps, and evidence, helping explain repeated retries or stalled progress.