$ loading_
Check live messages, recover recent codes, and verify the exact source inspected.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "messages-ops" skill from askskill: 1. Download https://raw.githubusercontent.com/affaan-m/ECC/main/skills/messages-ops/SKILL.md 2. Save it as ~/.claude/skills/messages-ops/SKILL.md 3. Reload skills and tell me it's ready
Please find any verification code I received in the last 10 minutes. Check local text messages first, and the sender may be a bank or login service. Tell me which source you inspected.
Returns the message source, likely sender or service, time window, and a clear status showing whether the code was found.
First review my recent DM thread with this contact on X, summarize the key point of their latest message, and state which thread source you checked. Do not draft a reply yet.
Returns the inspected platform and thread, a summary of the latest message, the time window, and a status such as read or awaiting reply draft.
Check whether there is a new message from the client, and clearly state whether you inspected text messages, X DMs, or another messaging surface. If login or MFA blocks access, report the exact blocker.
Returns the inspected message source, relevant sender or thread, the retrieval result, and an explicit blocked or completed status.
When a user urgently needs to complete sign-in or verification, this skill focuses on recent local messages and narrows the search by service or sender. The result clearly states the inspected source and status.
When the next step depends on the latest inbound message, this skill reads the target thread first, identifies the latest message and open loop, and then decides whether to hand off to an outbound skill.
This fits situations where you need proof of what was actually checked. It reports the message platform, thread or sender, time window, and whether the status is read, code-found, or blocked.
The documentation describes messages-ops as a workflow for live-message retrieval, including text messages, DMs, recent one-time code lookup, and thread inspection before a follow-up. It stresses resolving the exact message surface, sender or thread, and time window first, then reading or searching in a focused way. Outputs should clearly state the source used, relevant thread or sender, the time window, and an explicit final status such as read, code-found, blocked, or awaiting reply draft.
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
It handles live-message retrieval tasks such as reading texts, checking DM threads, recovering recent one-time codes, or inspecting a conversation before replying. A key requirement is stating the exact message source that was checked.
This skill is not for mailbox work. If the dominant surface is a mailbox, you should use email-ops instead; messages-ops focuses on texts, DMs, and other messaging surfaces.
If authentication or MFA blocks access to the messaging surface, the exact blocker should be reported instead of repeatedly retrying vaguely. The final state should be explicitly marked as blocked.
Design reliable deployment workflows, CI/CD pipelines, and production release strategies.
Orchestrate parallel AI agent workflows with dmux for faster development execution.
Helps developers follow this JavaScript repository's coding, testing, and commit conventions.
Apply modern, safe, idiomatic C++ standards for writing, review, and refactoring.
Search PubMed literature, MeSH terms, PMIDs, and citation data efficiently.
Audit, plan, and implement SEO improvements for better search visibility.
Organize inboxes, draft emails, verify sending, and follow up safely.
Fuzzy-search and browse Apple Messages by contact, date, and conversation context.
Run repo tasks, debug CI, and deliver fixes with verified evidence.
Read, send, search, and manage messages across multiple chat platforms.
Securely retrieve, decrypt, search, and audit WeCom chat records.
Research current facts, compare options, and produce evidence-based recommendations.