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.
Best use case
messages-ops is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using messages-ops should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/messages-ops/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How messages-ops Compares
| Feature / Agent | messages-ops | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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
Related Skills
x-api
X/Twitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.
workspace-surface-audit
Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Gemini CLI or understanding what capabilities are actually available in their environment.
visa-doc-translate
Translate visa application documents (images) to English and create a bilingual PDF with original and translation
videodb
See, Understand, Act on video and audio. See- ingest from local files, URLs, RTSP/live feeds, or live record desktop; return realtime context and playable stream links. Understand- extract frames, build visual/semantic/temporal indexes, and search moments with timestamps and auto-clips. Act- transcode and normalize (codec, fps, resolution, aspect ratio), perform timeline edits (subtitles, text/image overlays, branding, audio overlays, dubbing, translation), generate media assets (image, audio, video), and create real time alerts for events from live streams or desktop capture.
video-editing
AI-assisted video editing workflows for cutting, structuring, and augmenting real footage. Covers the full pipeline from raw capture through FFmpeg, Remotion, ElevenLabs, fal.ai, and final polish in Descript or CapCut. Use when the user wants to edit video, cut footage, create vlogs, or build video content.
verification-loop
Comprehensive verification system for code changes
unified-notifications-ops
Operate notifications as one ECC-native workflow across GitHub, Linear, desktop alerts, hooks, and connected communication surfaces. Use when the real problem is alert routing, deduplication, escalation, or inbox collapse.
ui-demo
Record polished UI demo videos using Playwright. Use when the user asks to create a demo, walkthrough, screen recording, or tutorial video of a web application. Produces WebM videos with visible cursor, natural pacing, and professional feel.
token-budget-advisor
Offers the user an informed choice about how much response depth to consume before answering. Use this skill when the user explicitly wants to control response length, depth, or token budget. TRIGGER when: "token budget", "token count", "token usage", "token limit", "response length", "answer depth", "short version", "brief answer", "detailed answer", "exhaustive answer", "respuesta corta vs larga", "cuántos tokens", "ahorrar tokens", "responde al 50%", "dame la versión corta", "quiero controlar cuánto usas", or clear variants where the user is explicitly asking to control answer size or depth. DO NOT TRIGGER when: user has already specified a level in the current session (maintain it), the request is clearly a one-word answer, or "token" refers to auth/session/payment tokens rather than response size.
terminal-ops
Evidence-first repo execution workflow for ECC. Use when the user wants a command run, a repo checked, a CI failure debugged, or a narrow fix pushed with exact proof of what was executed and verified.
team-builder
Interactive agent picker for composing and dispatching parallel teams
tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.