inbox-triage skillA
inbox-triage is agent-read markdown (skill) from nano-muse/nanomuse: 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..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# 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 …
Read the whole file at its exact version.
How to install
mdr add nano-muse/nanomuse/inbox-triage@v1mdr add nano-muse/nanomuse/inbox-triage@sha256:0542a46befff939fPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_ejor3zu433udldph)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2399 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
nano-muse/nanomuse · 6 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ejor3zu433udldph GET https://markdownregistry.com/api/v1/resolve?ref=nano-muse/nanomuse/inbox-triage GET https://markdownregistry.com/api/v1/blob/0542a46befff939f492bb4082c7713c743bd7bf9d70ca4f3e0a549aee37efa63
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from nano-muse/nanomuse
Every file in nano-muse/nanomuse