Workflow·Email

email-triage

Scans the inbox for recent emails, classifies them by priority tier, and offers reply drafting for check-email, inbox-triage, and morning…

You say
Buy it · $79 Read it before you buy $79 Written by ericporres · unverified publisher
Context cost
1.7k tokensestimated from the bundle, loaded when it triggers
Bundle
1 file · 6.8 kBtext throughout, nothing executable
Licence
MITpaid listing
Last change
no release on file
Servers it uses
Noneruns standalone

What it does

This skill should be used when the user asks to "check email", "triage my inbox", "check my email", "morning email", "inbox summary", or invokes /email or /summary. Scans the inbox for recent emails, classifies by priority tier, and offers reply drafting.

Installed, it changes the agent in these ways.

What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.

Workflow

Runs a procedure end to end.

emailinboxtriagereplies
Filed under

Email

The skill itself

This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md6.8 kB · 180 lines
--- name: email-triage description: > This skill should be used when the user asks to "check email", "triage my inbox", "check my email", "morning email", "inbox summary", or invokes /email or /summary. Scans the inbox for recent emails, classifies by priority tier, and offers reply drafting. ---
9# Email Triage Skill
10
11## Overview
12
13Scan Gmail for recent messages, classify them into three priority tiers, and offer to draft replies for urgent items.
14
15## Step 0 — Load Context (optional)
16
17If you use a family-assistant skill or maintain reference files with contact and alias data, load them here before scanning. This gives the triage engine context about who matters and which aliases map to which priority.
18
19Example reference files (if available):
20
21| File | What it provides |
22|------|-----------------|
23| family-members.md | Names, relationships, emails — always Tier 1 |
24| email-aliases.md | Alias routing & default priority tiers |
25| household.md | Schools, services — helps classify household emails |
26
27> **Tip:** The [family-assistant-skill](https://github.com/ericporres/family-assistant-skill) template is a good companion for this plugin. It provides the contact and household context that makes triage smarter.
28
29If you don't have reference files yet, the skill still works — it just classifies based on content and sender patterns instead of alias routing.
30
31## Step 1 — Scan Inbox
32
33Use Gmail MCP tools to search:
34
35```
36Query: in:inbox newer_than:1d
37```
38
39Add exclusions for any labels you handle separately (e.g., -label:AI if you have an AI newsletter digest).
40
41**Why not is:unread:** Many people casually browse emails on their phone without intending to act on them. Read status is unreliable as a triage signal. Use time-based windowing instead.
42
43**Time window options:**
44- Default: newer_than:1d (last 24 hours — good for daily morning triage)
45- "Just today": newer_than:12h
46- "Catch me up" or "this week": newer_than:3d
47
48**Snippet-first approach:** The search results include subjects, senders, and snippets. Classify from these first. Only call read_gmail_message for:
49- All Tier 1 emails (need full context for reply drafting)
50- Ambiguous Tier 2 emails where the snippet isn't enough to classify
51
52This avoids token blowout on high-volume days.
53
54## Step 2 — Classify into Tiers
55
56### Tier 1 — Reply Needed
57
58Emails with a direct question, request, or action aimed at you. Each gets:
59- One-line summary of what the sender needs
60- Suggested action: Reply / Schedule / Forward to [person]
61
62**Urgency signals (auto-promote to Tier 1):**
63- From family members or emergency contacts
64- From your work domain (e.g., @yourcompany.com)
65- Time-sensitive language: "by EOD", "deadline", "RSVP", "urgent", "asap", "tomorrow", "today"
66- Replies in threads you started
67- Financial: bills, invoices, payment due, bank alerts, fraud alerts
68- School emails: any school-related domains your kids attend
69- Medical: doctor's office, appointment confirmations, prescription alerts
70
71### Tier 2 — Review / Decide
72
73Needs your eyes but not necessarily a reply:
74- Order/shipping confirmations
75- Calendar invites
76- Shared documents
77- Travel itinerary changes
78- Receipts and transaction confirmations
79- Newsletters you actively read
80
81### Tier 3 — Noise
82
83Marketing, bulk newsletters, automated notifications, social media alerts, promotional offers. Summarize as counts by category.
84
85### Alias-aware routing (customize this section)
86
87If you use email aliases (e.g., shopping@yourdomain.com, travel@yourdomain.com), map them to default tiers here. This is the most powerful part of the triage — a well-configured alias map means most emails get classified instantly without needing to read content.
88
89Example alias routing:
90
91```
92Primary (you@domain.com) → Evaluate on content
93Family/kids aliases → Default Tier 1
94Financial aliases (bank@, 401k@) → Default Tier 1
95Health/medical aliases → Default Tier 1
96Household/utilities aliases → Default Tier 2
97Travel aliases → Default Tier 2
98Shopping aliases → Default Tier 3 (unless delivery update → Tier 2, fraud → Tier 1)
99Subscription/media aliases → Default Tier 3
100```
101
102> **Tip:** If you use the family-assistant-skill's email-aliases.md, you can list 100+ aliases with per-alias tier routing. The triage skill reads it at runtime and applies the mapping automatically.
103
104When an alias isn't recognized, fall back to content-based classification.
105
106## Step 3 — Present Results
107
108Format output as:
109
110```markdown
111# Inbox Triage — [Today's Date]
112[X emails scanned from last 24h]
113
114## Reply Needed (X)
115
1161. **[Sender Name]** — [Subject]
117 [One-line summary of what they need]
118 → Suggested: [Reply / Schedule / Forward to X]
119
1202. ...
121
122## Review (X)
123
124- **[Sender]** — [Subject] — [One-line summary]
125- ...
126
127## Noise (X)
128[X] marketing, [X] social, [X] automated, [X] promotional
129→ Want me to archive these?
130```
131
132**Numbering matters.** Tier 1 items are numbered so you can say "draft a reply to #3."
133
134## Step 4 — Reply Drafting (conversational)
135
136When asked to draft a reply (e.g., "draft a reply to #3"):
137
1381. Read the full message with read_gmail_message if not already loaded
1392. Read the full thread with read_gmail_thread for conversation context
1403. Draft a reply matching the user's voice (see guidelines below)
1414. Present the draft for review
1425. **Never auto-send.** Always require explicit confirmation before sending.
143
144### Email voice guidelines (customize these)
145
146Describe how you write emails so Claude can match your style:
147
148```
149- Direct and concise — no filler
150- Warm but professional
151- Uses first names
152- Signs off with "[Your Name]" or "Best, [Your Name]"
153- Doesn't over-explain or over-apologize
154```
155
156## Step 5 — Archive Offer
157
158If there are Tier 3 (noise) emails and the user confirms archival:
159- List the specific emails that will be archived
160- Require explicit confirmation
161- Archive only after confirmation
162- Report what was archived
163
164**Never auto-archive. Never permanently delete.**
165
166## Edge Cases
167
168- **Empty inbox:** "Nothing new in the last 24 hours — inbox is clean."
169- **All noise:** Skip to Tier 3 summary, note no action items.
170- **Very high volume (50+):** Warn the user, offer to scan in batches or filter by alias/sender.
171- **Thread context:** For Tier 1 thread replies, read the full thread to understand context before suggesting a response.
172
173## What This Skill Does NOT Do
174
175- Does not maintain its own contact list (optionally reads from family-assistant or similar)
176- Does not save output to files (ephemeral conversation view)
177- Does not send emails without explicit confirmation
178- Does not modify labels or filters
179- Does not permanently delete anything
180
In the file
SKILL.md1,033 words
Files1
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈80
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
1,620
on trigger
The instruction body, read only when the skill fires.
0.85%
of a 200k window
Ten skills this size would take about 9% of the window before you open a file.
050k100k150k200k context window

1.7k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Middling. Fine to keep on in a project where you use it weekly, worth unloading in one where you never do.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

Adoption
Installsnone yet
Ratingno reviews yet

The procedure it runs

The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It writes no files and reaches no network. All it changes is how the model reasons and writes.

What it asks for
Writes filesno
Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

If this is not it

13 other skills in Email

What is in the bundle

1 file, 6.8 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md6.8 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 1 file you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

$79 once
email-triage · MIT · ericporres
one-time
Price$79 once
LicenceMIT — the author’s, unchanged by this purchase
Paid throughStripe, once, on the card you add at the checkout
Keeps workingfor good — the files are yours once they are on disk
Updatesevery update its author ships, delivered through this account

You can read the whole bundle before paying — the SKILL.md above is the product, not a preview of it. What the money buys is the delivery: the folder packaged and handed to your machine by key, every update its author ships, and our support if it does not do what this listing says. The terms of use are MIT, set by the author and unchanged by buying it here.

Payment runs through Stripe, on a page like this one rather than a redirect. Once there is an account it joins the same mcprush invoice as everything else you run, so there is never a second card to enter.

Which clients pick it up on their own

A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.

Claude Code.claude/skills/
Claude Desktop
ChatGPT
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok.grok/skills/
Zed.agents/skills/
Windsurf.windsurf/skills/
Agent SDK.claude/skills/
HTTP / API
This release
Versionnot versioned
Publishedno release date on file
Price$79
Referenceericporres/email-triage

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v
  • No earlier releases have been published to the marketplace.
Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

no reviews yet · no installs yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Who can post

Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.

Who wrote it

ER
ericporres

Publishes on mcprush.

0 servers listed1 skill listednot claimed
Profile
Publisher
Servers0