Triage an inbox
Sorts a batch of emails into reply, delegate, schedule and archive by your priorities, flags suspicious messages, and drafts the short replies and delegation notes.
Inbox triage is a sequence of fast decisions, one per message: reply now if it takes a couple of minutes, delegate it if someone else should own it, schedule it if it needs real time or a later date, archive it if no action is needed. The value is in getting each decision right against what matters this week, catching the hidden deadline in a long thread, and not letting a phishing email or a vague "quick question" jump the queue.
Triage these emails:
Only if [PRIORITIES] is given: My priorities and delegates:
- If the input contains no recognisable emails, ask for them and stop.
- For each email, identify the sender, what is being asked of me, any deadline stated in the email, and how it relates to my priorities.
- Assign exactly one bucket:
- Reply: needs my response and it can be written in about two minutes.
- Delegate: someone else should own it. Name the delegate only if my priorities say who handles this; otherwise write
[who?]. - Schedule: needs me but more than a few minutes of work or thought, or not until a later date. Estimate the time it needs and when to do it, before any deadline.
- Archive: information only, newsletters, notifications, resolved threads or requests I have said to ignore.
- Check each email for signs of phishing or fraud: urgency plus a link or attachment, requests for credentials, payment or gift cards, changed bank details, a sender name that does not match the address, or an unexpected invoice. Give these the bucket "Suspicious" in the triage table instead of one of the four, explain the signs in the Suspicious section and how to verify through a known channel (a number you already have, not one in the email); never draft a reply that complies. A routine invoice from a supplier I already use is not suspicious by itself; changed payment details or an unknown supplier are.
- Order the triage table by urgency: hard deadlines first, then items tied to my priorities, then the rest.
- Draft each Reply in under 80 words, and a one or two line forwarding note for each Delegate.
- Do not invent deadlines, facts or my decisions. Write deadlines as the email states them ("Friday", "5pm tomorrow"); do not convert them to calendar dates you cannot confirm. When a reply needs a decision I have not given, draft it with a
[decide: …]placeholder. - Drafts must not commit me to meetings, money or deliverables unless my priorities say so.
- If there are more than 30 emails, triage the 30 most urgent and list the rest by subject with a suggested bucket only.
Triage
A table: # | From | Subject | Bucket | Why (one line) | Deadline.
Draft replies
For each Reply item: "#n to <sender>", then the draft.
Delegate
For each Delegate item: delegate, then the forwarding note.
Schedule
For each Schedule item: what it needs, time estimate, suggested slot.
Suspicious
Each flagged email with the warning signs and how to verify it. "None" if none.
1 required value still a placeholder; the assistant will ask for it.
details
- kind
- Prompt: a task you run by name to get one finished thing back
- domain
- Writing and communication
- category
- level
- Beginner
- made for
- People manager, Executive / leader, Founder / business owner, Anyone, personal use
- risk
- read-only
- version
- v1.0.1 · experimental
- reviewed
- 2026-10-02
- works in
- Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai
use in
npx @hermes-hq/hodios install triage-inbox --target claude-codenpx skills add hermes-hq/hodios-dist --skill triage-inbox -a claude-codeclaude plugin marketplace add hermes-hq/hodios-distclaude plugin install hodios-writing-communication@hodiosThe plugin brings every entry in this domain at once.
pairs well with
All of EmailReply to an email
Drafts a reply that answers every question and request in a received email from your stated position, matches its formality, proposes next steps and flags points you have not decided.
reply-to-emailWrite a professional email
Drafts an email from rough intent with a specific subject line, the ask in the first two sentences and the right tone for the relationship, marking any detail it would otherwise have to invent.
write-professional-emailDecline a request gracefully
Declines a request or invitation clearly and kindly in the first lines, gives an honest brief reason if wanted, offers only real alternatives and preserves the relationship.
decline-request-gracefullyBuild a personal email template library
Builds a personal library of reusable email templates for the user's recurring situations, in their own voice from sent examples, with placeholders, subject lines and when-to-use notes.
build-email-templatesRequest approval by email
Writes a bottom-line-first email asking a busy decision-maker to approve a budget, purchase, hire or exception, with options, cost, the risk of waiting and a one-line reply path.
request-approval-by-emailRespond to an angry email
Drafts a reply to an angry email that de-escalates, acknowledges what is valid, corrects facts without defensiveness and sets a clear next step, with a note on whether to call instead.
respond-to-angry-email