Rebundle
/inbox-zero
Skill

Inbox Zero

Triage de los últimos 50 emails: clasifica en buckets accionables y propone respuestas en tu tono.

SKILL.md
---
name: inbox-zero
description: Triage the user's last 50 unread emails into Urgent / Action / Info / Newsletter / Spam buckets. For Urgent and Action, draft a reply in the user's tone. Output a structured summary with counts, top 3 priorities, and a suggested time block plan. NEVER send emails — only read, classify, archive (when allowed), and prepare drafts in the user's drafts folder. Always show the classification before any side effects so the user can override.
---

Inbox Zero

A skill that pulls the latest 50 unread emails from the connected mail provider, classifies each into one of five buckets, prepares drafts for the actionable ones, and produces a tight summary the user can scan in 30 seconds.

When to use this skill

  • The user opens their inbox and there are 30+ unread items.
  • The user is back from PTO with a flooded inbox.
  • Closing the day and the user wants to triage before logging off.

If the user mentions "triage email", "process inbox", "deal with email", or "clear inbox", this skill applies.

Required tools

  • A connected mail provider via MCP (Gmail, IMAP, or Outlook).
  • Read access to the last 50 unread messages (subject, from, body, received date, thread).
  • Write access to the drafts folder (never the send action).

If the user has no mail MCP connected, stop and ask which provider they use before proceeding.

Buckets

Classify each email into exactly one bucket:

  • Urgent — requires user action within 4 hours. Examples: signed contract today, payment failed, customer escalation, on-call alert.
  • Action — requires response or task but can wait until tomorrow. Examples: customer questions, peer reviews, scheduling.
  • Info — read-only, no action. Examples: status updates, FYI cc, automated reports the user wants to skim.
  • Newsletter — subscribed content. Examples: Substack, LinkedIn news, Product Hunt.
  • Spam — generic outbound, phishing, sender outside the user's networks asking for money or credentials.

When in doubt between Urgent and Action, prefer Action. Only flag Urgent if the message explicitly states a deadline within hours, mentions money/legal/security, or is from a person the user has marked as VIP.

Drafting replies

For Urgent and Action emails:

  1. Read the user's last 5 sent emails to learn their voice (length, formality, sign-off).
  2. Match the original language of the incoming email (Spanish in, Spanish out).
  3. Keep the draft under 6 sentences.
  4. Never invent commitments, dates, prices, or facts. If you need information the user has not provided, leave a placeholder like [FALTA: confirmar fecha] and surface it in the summary.

Save drafts in the drafts folder. Do not send.

Output format

Inbox Zero · {N} emails procesados

Urgente ({n}):
- {sender}, {company} — {one-line context}. Draft listo.

Acción ({n}):
- {sender} — {one-line context}.

Info ({n}) · archivados.
Newsletter ({n}) · marcados como leídos.
Spam ({n}) · eliminados.

Sugerencia: dedica los próximos {X} minutos a los {Y} urgentes
y agenda los {Z} de Acción para mañana entre {hora} y {hora}.

Constraints

  • Never send. Drafts only.
  • Never delete unless the bucket is Spam and the sender domain is on a known spam list.
  • Never share email content with third-party tools.
  • If a draft contains a placeholder ([FALTA: …]), call it out in the summary so the user fills it before sending.

Failure mode

If the mail provider is unreachable, return early with a clear error and do not invent classifications.