/skill

Message Operations

Created by ECC. Credit to the original author and project.

Use this skill for live message tasks. This includes texts, direct messages, recent one-time codes, and thread checks before the next step.

This skill is not for email. Use email-ops when the main source is an inbox.

Related Skills

Use these ECC skills when they fit:

• email-ops when the source is email
• connections-optimizer when a direct message is part of outreach
• lead-intelligence when a live thread should guide who to contact or how to start
• knowledge-ops when the user asks to save useful thread details for later

Do not switch skills only because a message names an email address. Check where the message was received.

When to Use This Skill

Use it when the user asks to:

• Read messages, texts, or direct messages
• Find a recent sign-in or one-time code
• Check a thread before writing a reply
• Name the source, sender, thread, or time checked

Safety Rules

• Name the source before you claim that you checked it.
• Use only the source the user asked for.
• If the source is not clear, ask which app or service to check.
• Use an approved helper or normal access path when one exists.
• Do not open raw message files or message databases unless the user clearly asks and no safe helper exists.
• Read only the messages needed for the task.
• Treat one-time codes as private. Return only the needed code and basic source details.
• Do not send a reply unless the user clearly asks you to send it.
• If the user asks for a draft, draft it but do not send it.
• Do not mark a message as read, delete it, archive it, or change the thread unless asked.
• If sign-in or two-step checks block access, stop and state the exact block.
• Do not keep trying the same blocked sign-in path.

Steps

1. Set the Scope

Before you act, find:

• The message app or service
• The sender, receiver, thread, or service name
• The time range
• The task type: find, read, check, draft, or send

If one detail is missing but the task is still clear, use the smallest safe scope. For example, search recent texts from the named bank.

2. Read Before You Draft

If the task may lead to a reply:

1. Read the newest incoming message.
2. Read enough earlier messages to understand it.
3. Note any open question, promise, date, or next step.
4. Draft a reply only if asked.
5. Hand off to a related skill only when it fits the task.

Do not guess what the thread says.

3. Find One-Time Codes Fast

For a one-time code:

1. Search recent local messages first.
2. Limit the search by service or sender when known.
3. Check the newest matching message first.
4. Make sure the code is recent and matches the named service.
5. Stop when the code is found or the narrow search is done.

If two codes match, return the newest one and note that an older code also exists. Do not assume an old code still works.

4. Report the Evidence

State:

• The source you checked
• The sender, thread, or service, when known
• The time range you checked
• A short result
• One exact status:
  • Read
  • Code found
  • Not found
  • Blocked
  • Draft ready
  • Sent

Never use Sent unless the send action was confirmed.

Output Format

Source
- App or service:
- Sender, thread, or service:
- Time range:

Result
- Short message summary or one-time code:

Status
- Read / Code found / Not found / Blocked / Draft ready / Sent

For a blocked task, add:

Block
- Exact reason:
- What the user must do next:

Example

User request:

Find the latest login code from Acme in my texts.

Good result:

Source
- App or service: Local text messages
- Sender, thread, or service: Acme
- Time range: Last 15 minutes

Result
- One-time code: 482193
- Received: 2 minutes ago

Status
- Code found

If access is blocked:

Source
- App or service: Local text messages
- Sender, thread, or service: Acme
- Time range: Last 15 minutes

Result
- I could not read the thread.

Status
- Blocked

Block
- Exact reason: The message app needs sign-in approval.
- What the user must do next: Approve the sign-in, then ask me to try again.

Common Mistakes

• Do not treat email as a text or direct message.
• Do not claim a search happened when the source was not known.
• Do not run a wide search for a recent code.
• Do not show extra private messages when one result is enough.
• Do not use an old code when a newer code exists.
• Do not draft or send a reply before reading the latest thread.
• Do not hide a sign-in or access block.
• Do not say a reply was sent without proof.

Final Check

Before you answer, make sure:

• The message source is named.
• The sender, service, thread, or exact block is named.
• The time range is clear.
• The result does not expose extra private data.
• The status is exact.
• No message was sent or changed without clear user approval.