Messages Ops
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.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Messages Ops when an AI agent needs a reusable SKILL.md workflow for this job: 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.
When not to use it
Skip Messages Ops when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/messages-ops # Save SKILL.md to ~/.claude/skills/messages-ops/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/messages-ops/SKILL.md. For a shared project, commit the folder at .claude/skills/messages-ops/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Messages Ops skill for this task: user says "read my messages", "check texts", "look in DMs", or "find the code". Confirm any required inputs or files before making changes.
What supports this recommendation?
72/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 74/100
- Source evidence
- 63/100
- Source signals
- 70/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# 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
```text 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
Intended uses
- 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
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.