agentleFS
Ootto-AIOotto-AI/claude-inbox-skills/skills/inbox-triage/SKILL.md

inbox-triage

Skill1 starsChanged 5 months agoMITView on GitHub

Sort a full inbox into reply-now / later / ignore, with drafts for the urgent ones. Use when the user says "triage my inbox", "sort my emails", "inbox triage", "what should I reply to", "clear my inbox", or "which emails need a response".

53 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use aeon-update, auto-workflow and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • aaronjmarsSkill

    aeon-update

    Pull framework updates from the upstream Aeon repo into this instance - 3-way merges canon's new commits into a PR, never clobbering operator config.

    Also in 4 projects that use this

  • aaronjmarsSkill

    auto-workflow

    Two-mode aeon.yml workflow builder - analyze inspects URLs and emits a tiered, signal-verified skill-enablement plan plus an aeon.yml diff; enable flips slugs to enabled:true and opens a PR.

    Also in 4 projects that use this

  • +10 more from aaronjmars

The file

Files
SKILL.md

Inbox Triage

Sort a full inbox into reply-now / later / ignore, with drafts for the urgent ones.

When to use

Your inbox is full and you need to know what actually needs a response today, what can wait, and what to archive — plus ready-to-send drafts for the urgent ones.

What you'll need

A list of unread emails (sender, subject, and a line or two of each message — paste as many as you want).

Instructions

Collect any missing inputs from the user, then run this prompt:

You are my executive assistant triaging my inbox. Below is a list of unread emails, each with sender, subject, and a short preview.

[paste your emails here — one per block, with sender, subject, and preview]

Sort every email into exactly one of three buckets:
1. REPLY NOW — needs a response today (a real person waiting, a deadline, money, or a decision blocked on me)
2. LATER — matters but can wait this week (FYIs I should read, low-urgency requests)
3. IGNORE — newsletters, promos, automated notifications, or anything I can safely archive

For each email give one short line: sender — why it's in that bucket.
Then, for every REPLY NOW email only, write a ready-to-send draft reply: plain, friendly, professional, 2-4 sentences, no filler. If a reply needs information only I have, leave a clearly marked [blank] for me to fill.

Output as three headed sections (Reply Now, Later, Ignore), with the drafts under each Reply Now item.

Tip: Paste the actual preview text, not just subject lines — the more of each message Claude can see, the better it judges urgency and writes a usable draft.


Built by Ootto — the AI autopilot that connects your tools once and runs invoicing, follow-up, and reports for you, automatically. Book a demo →

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.