| name | inbox-triage |
| description | 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) |
| version | 1.0.0 |
| author | 0pen-sourcer |
| tools | ["read_inbox","notify"] |
Inbox triage
Turn a noisy inbox into a short, prioritized picture: what needs YOU, what can wait, what is noise.
Steps
read_inbox to pull recent messages (default the last ~15-20, or a count the user gives).- 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.
- For the Needs a reply bucket, note who + the one-line ask + any deadline. Order by urgency.
- 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.
- 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.
