Claude Skill

inbox-triage

Go through recent mail and sort it into needs-a-reply, waiting-on-others, to-do and can-ignore, with draft replies ready for review. Use when the user asks to triage, sort, catch up on or clear their inbox — never to send anything on its own.

LLM Mart · 0 points · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download nano-muse-nanomuse-nanomuse_skills_builtin_inbox-triage-d810baa.zip · 1 KB

nano-muse/nanomuse 16 3 forks GPL-3.0 Updated 1d ago

Part of nano-muse/nanomuse — 11 skills

Install

skills CLI npx skills add https://github.com/nano-muse/nanoMuse/tree/main/nanomuse/skills/builtin/inbox-triage

Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install nano-muse-nanomuse@llmmart

Git git clone https://github.com/nano-muse/nanoMuse.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole nano-muse/nanomuse collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Inbox triage

Needs the mail connector (read_emails). If it is not available, say so and stop.

Read

read_emails with unread_only=true first (up to 50). If there are fewer than 10, read the last 3 days with unread_only=false too, so nothing waiting since yesterday is missed.
For each sender the user has written to before, contacts action=search gives the name and company; use names, not addresses, in what you write.
recall "inbox" and "email" for the user's rules: senders that always matter, newsletters they keep, how they like replies to sound.

Sort

Every message lands in exactly one group:

Reply needed — someone asked the user something, or is waiting.
Waiting on them — the user asked, no answer yet; note how long.
To do — no reply needed, but an action is: pay, book, read a document, show up somewhere.
Read later — newsletters, notifications, receipts.
Ignore — clear spam, expired offers, automated noise.

Threads with the same subject count once. Anything that mentions money, a deadline, a contract or health goes to the top of its group.

Draft, do not send

For each Reply needed mail, write a reply the user could send as is: their voice (from memory), short, answering the actual question. Put all drafts in one file, mail/drafts-YYYY-MM-DD.md, one section per thread with To, Subject, the draft, and a one-line note on what you were unsure about.
Do not call send_email in this job unless the user tells you, mail by mail, to send. A reply the user approves later is a separate step.

Report

In chat, a short list per group: sender name — subject — what it is about in a few words (groups 4 and 5 as counts only). Then the file with the drafts, and the two or three things that should not wait. Deadlines or events found in the mail: offer to set a reminders or draft a calendar event; do it only when the user says yes.

If the user corrects a sorting decision ("newsletters from X I read"), remember it so the next triage gets it right.

Files (nanomuse)

SKILL.md 2.4 KB

---
name: inbox-triage
description: Go through recent mail and sort it into needs-a-reply, waiting-on-others, to-do and can-ignore, with draft replies ready for review. Use when the user asks to triage, sort, catch up on or clear their inbox — never to send anything on its own.
channel: api
metadata:
  author: nanoMuse
  version: "1"
---

# Inbox triage

Needs the mail connector (`read_emails`). If it is not available, say so and stop.

## Read

- `read_emails` with `unread_only=true` first (up to 50). If there are fewer than 10, read the last 3 days with `unread_only=false` too, so nothing waiting since yesterday is missed.
- For each sender the user has written to before, `contacts` action=search gives the name and company; use names, not addresses, in what you write.
- `recall` "inbox" and "email" for the user's rules: senders that always matter, newsletters they keep, how they like replies to sound.

## Sort

Every message lands in exactly one group:

1. **Reply needed** — someone asked the user something, or is waiting.
2. **Waiting on them** — the user asked, no answer yet; note how long.
3. **To do** — no reply needed, but an action is: pay, book, read a document, show up somewhere.
4. **Read later** — newsletters, notifications, receipts.
5. **Ignore** — clear spam, expired offers, automated noise.

Threads with the same subject count once. Anything that mentions money, a deadline, a contract or health goes to the top of its group.

## Draft, do not send

- For each *Reply needed* mail, write a reply the user could send as is: their voice (from memory), short, answering the actual question. Put all drafts in one file, `mail/drafts-YYYY-MM-DD.md`, one section per thread with *To*, *Subject*, the draft, and a one-line note on what you were unsure about.
- Do not call `send_email` in this job unless the user tells you, mail by mail, to send. A reply the user approves later is a separate step.

## Report

In chat, a short list per group: sender name — subject — what it is about in a few words (groups 4 and 5 as counts only). Then the file with the drafts, and the two or three things that should not wait. Deadlines or events found in the mail: offer to set a `reminders` or draft a `calendar` event; do it only when the user says yes.

If the user corrects a sorting decision ("newsletters from X I read"), `remember` it so the next triage gets it right.