Check Inbox — triage unread email

Apply this skill when the user asks about the state of their Yandex inbox.

Steps

1. Call mcp__yandex-mail__get_unread_emails with limit=10 (or larger if the user explicitly asks for "all" / "more"). If zero results — reply briefly "Непрочитанных писем нет" / "Inbox is clean" and stop.

2. For each email parse from, subject, and the first ~200 chars of body, then assign:

   Category (pick one):

   • business — clients, deals, contracts, invoices
   • project — ongoing work, internal coordination
   • financial — banks, accounting, tax, payments
   • personal — non-work correspondence
   • notification — automated system messages, receipts, status updates
   • marketing — newsletters, promotions, ads
   • unknown — too little context to categorise; mark explicitly, don't guess

   Urgency:

   • 🔴 needs reply — direct question, deadline, payment request, action requested
   • 🟡 should read — important info, no immediate reply
   • ⚪️ can ignore — newsletter, generic notification, ad

3. Present a structured summary in this format:

   Непрочитанных: N
   
   🔴 NEEDS REPLY (M):
     • [UID 1234] From <sender> · <category>
       <one-line summary of the ask + any deadline>
   
   🟡 SHOULD READ (K):
     • [UID 1235] From <sender> · <category>
       <one-line summary>
   
   ⚪️ CAN IGNORE (L):
     • <sender> — <one-line label>

4. End with a one-line recommendation: which message to act on first and why.

Rules

• Do not mark anything read automatically. get_unread_emails uses BODY.PEEK[] so the \Seen flag is not set. If the user wants to mark a specific message read, they will ask — then call mcp__yandex-mail__mark_as_read with the UID.
• Do not invent facts. If the subject or sender is unclear, mark the category as unknown and say so honestly.
• Cyrillic in subject/body is already decoded by the server — do not re-decode.
• No emoji or formatting flourishes beyond the urgency markers — keep the output scannable.
• One category per email — if it could fit two, pick the one that matters more for the user's role (typically: business > project > financial > notification).

Drilling deeper

If the user asks for the full text of a specific message (e.g. "show me UID 1234 in full" / "что в письме 1234"), call mcp__yandex-mail__get_email with that UID and show the full body and attachments list.

Heuristics for common automated senders

These map to notification + ⚪️ unless the body clearly indicates otherwise (e.g. an actual transaction confirmation matters → financial + 🟡):

• noreply@*, no-reply@*, notifications@*, mailer-daemon@*
• LinkedIn, GitHub, GitLab digests
• Calendar invites without an explicit ask are 🟡; if they conflict with existing commitments, escalate to 🔴

The user can override these by name — track their corrections within the conversation.