messages-ops

Use it when:: You ask the agent to check your texts or DMs, find a code that just arrived, or read a thread before a follow-up.
It does:: Settles the surface, sender, service and time window first, searches only the recent window for a code, and stops once it's found.
You get:: The source checked, the sender or thread, a summary or the code, and a status: read, code-found, blocked or awaiting reply draft.
Hands off:: Mailbox work to email-ops, and any reply to an outbound skill.

Reads your private messages and one-time codes through whatever access your agent has to iMessage or DMs; the SKILL.md doesn't set that access up.

TL;DR

The texting and DM counterpart of ECC's email-ops. It covers live message retrieval from local messages such as iMessage, X and other social DMs, or another message surface behind a browser login. The agent first settles which surface, sender or service and time window, and whether you want retrieval, inspection or prep for a reply. If a reply may follow, it reads the latest inbound message, finds the open loop and hands off to the right outbound skill. For one-time codes it searches the recent local window, narrowed by service or sender, and stops as soon as the code turns up or the focused search is exhausted. It never claims a thread was checked without naming the source, prefers a known helper or standard path over improvised raw database access, and reports an auth or MFA block plainly instead of retrying it.

Summarizes the skill at d2ef268.

npx skills add https://github.com/affaan-m/ecc --skill messages-ops

skills.sh page Source on GitHub All skills from affaan-m/ecc

Total Downloads: 5,300 on skills.sh, Nov 9, 2026
Repo stars: 299,776 affaan-m/ecc
First seen: May 19, 2026 on skills.sh

Weekly Downloads

436

+71% over the 8 weeks to Nov 9

Weekly values

Week to	Installs
Sep 21	255
Sep 28	158
Oct 5	136
Oct 12	225
Oct 19	404
Oct 26	397
Nov 2	464
Nov 9	436

Category	category:documents category:personal Office files, notes and suites like Lark and Google Workspace. Learning and everyday help outside work.
Type	type:workflow A multi-step process the agent follows: interview, debug, run a TDD loop, review.
Effect	effect:none Adds no side effects of its own. It shapes how the agent thinks, writes or reviews. Guidelines and routers are always effect:none, even when the task they support edits code.
Needs	needs:account An account, API key or paid plan with an outside service.
Publisher	by:community Everyone else. Unverified vendor claims default to community.
Topics	messaging personal

SKILL.md

From affaan-m/ecc at d2ef268. Checked daily, last changed Nov 6, 2026.

Frontmatter

name: messages-ops
description: 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.
metadata:
  origin: ECC

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 latest inbound
identify the open loop
then hand off to the correct outbound skill if needed

3. Handle codes as a focused retrieval task

For one-time codes:

search the recent local message window first
narrow by service or sender when possible
stop once the code is found or the focused search is exhausted

4. Report exact evidence

Return:

source used
thread or sender when possible
time window
exact status:
- read
- code-found
- blocked
- awaiting reply draft

Output Format

SOURCE
- message surface
- sender / thread / service

RESULT
- message summary or code
- time window

STATUS
- read / code-found / blocked / awaiting reply draft

Pitfalls

do not blur mailbox work and DM/text work
do not claim retrieval without naming the source
do not burn time on broad searches when the ask is a recent-code lookup
do not keep retrying a blocked auth path without surfacing the blocker

Verification

the response names the message source
the response includes a sender, service, thread, or clear blocker
the final state is explicit and bounded