---
name: triage-my-inbox
description: Triage a batch of emails into Act now / Reply soon / Read later / Ignore, summarize each in one line, and draft short replies for anything that needs one. Use when the user asks to triage, sort, clean up, or catch up on their inbox.
license: MIT
metadata:
  library: TriedSkills
  job: Triage my inbox
  version: "1.1"
---

# Triage my inbox

## Inputs
- A set of emails (pasted text, exported .eml/.json, or read through a connected mail tool). Each needs at least: sender, subject, date, body.
- Optional: the user's priorities (e.g. "family and bills first", "I'm traveling until Friday").

## Steps
1. Read every email. Do not skip any; count them and report the count.
2. Put each email into exactly one bucket:
   - **Act now**: a deadline within 72 hours, money or account at risk, or a direct request from a real person waiting on the user.
   - **Reply soon**: a real person expects an answer, but nothing breaks if it waits a few days.
   - **Read later**: useful information, no action needed.
   - **Ignore / unsubscribe**: marketing, automated noise, duplicates.
3. **Check for phishing.** Flag any email that asks for credentials, payment, or gift cards through a link or an unusual channel, or whose sender domain doesn't match the brand it claims. Never recommend clicking those links. Tell the user to verify by going to the company's site directly.
4. For each email in Act now or Reply soon, write a one-line summary and the specific next action (with any deadline).
5. Draft replies (under 80 words each) for emails that need a reply. Write them in the user's voice: plain and polite. Leave `[brackets]` for facts you don't know. Never invent commitments, dates, amounts, items, or requests.
   - **Draft audit (required):** every concrete detail in a draft (a date, an item, a plan, a request) must appear in the original email or be a `[bracket]`. Delete anything else, including friendly filler that adds facts (e.g. "I'll bring snacks", "text me when you're on your way").
   - If a reply depends on a decision the user hasn't made (yes or no), give both versions instead of choosing.
6. End with a checklist: a numbered list of actions, earliest deadline first.

## Output format
A table (Bucket | From | Subject | One-line summary | Next action), then the draft replies, then the checklist.

## Guardrails
- Never send, delete, archive, or unsubscribe on your own. Only propose; the user approves.
- Don't open attachments or links from flagged emails.
- If the user's date isn't given, state the date you assumed when you judged deadlines.