# Inbox Triage

> Read recent email and sort it into what actually needs a reply (use when the user asks what's in their inbox / to triage their email)

- Skill: `0pen-sourcer/inbox-triage` (Agent Skill)
- Install (CLI): `npx skillmds@latest add 0pen-sourcer/inbox-triage`
- Raw SKILL.md: https://api.skillmd.com/api/skills/0pen-sourcer/inbox-triage/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: 0pen-Sourcer (https://skillmd.com/u/0pen-sourcer)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/0pen-sourcer/inbox-triage

---


# Inbox triage

Turn a noisy inbox into a short, prioritized picture: what needs YOU, what can wait, what is noise.

## Steps

1. `read_inbox` to pull recent messages (default the last ~15-20, or a count the user gives).
2. Bucket each one:
   - **Needs a reply** — a real person asking something, or an action with a deadline.
   - **FYI** — useful but no action (updates, receipts, confirmations).
   - **Noise** — newsletters, promos, automated notifications.
3. For the **Needs a reply** bucket, note who + the one-line ask + any deadline. Order by urgency.
4. Report a tight summary:
   - "N need a reply" — list them, most urgent first.
   - "M FYI" — one line total, do not enumerate.
   - "K noise" — just the count.
5. If the user wants to be reminded, offer to set a reminder or `notify` for the urgent ones. Do not send replies unless asked.

## Don't

- Don't send, delete, or archive anything — this skill only reads and summarizes.
- Don't enumerate every newsletter; the user wants signal, not their inbox re-listed.
- Don't guess at private content — summarize what the subject and preview actually say.
- Don't mark something "urgent" without a real deadline or ask behind it.