mail-triage
Skill7 starsChanged 9 months agoMITView on GitHub
Intelligent inbox triage — surface the most important emails across all accounts, prioritized by urgency and requiring attention. Use when user wants a smart overview of what needs their attention, asks "what's important in my email", or wants help deciding what to read first. Arguments: optional time window (default: last 48 hours) or account filter.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- gaofeng21cn/opl-skillstheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- gaofeng21cn/opl-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository32 other files it gives its agents.
- calendar-accountsSkill
- calendar-attendeesSkill
- calendar-conflictsSkill
- calendar-coreSkill
- calendar-eventSkill
- calendar-freeSkill
- calendar-recurringSkill
- calendar-searchSkill
- calendar-statsSkill
- calendar-todaySkill
- calendar-upcomingSkill
- mail-accountsSkill
- mail-action-itemsSkill
- mail-attachmentsSkill
- mail-bankingSkill
- mail-contactsSkill
- mail-coreSkill
- mail-digestSkill
- mail-expensesSkill
- mail-fromSkill
- mail-meetingsSkill
- mail-needs-replySkill
- mail-newsletterSkill
- mail-readSkill
- mail-searchSkill
- mail-securitySkill
- mail-statsSkill
- mail-subscriptionsSkill
- mail-threadSkill
- mail-top-sendersSkill
- mail-travelSkill
- mail-workSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 81
If you sent something in this thread → higher priority (someone replied to you).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Mail Triage — Smart Priority Overview
Triaging: $ARGUMENTS (default: last 48 hours)
Step 1: Pull all candidate emails
DB="$HOME/Library/Mail/V10/MailData/Envelope Index"
SINCE=$(($(date +%s) - 172800)) # 48 hours; adjust per $ARGUMENTS
sqlite3 "$DB" "
SELECT datetime(m.date_received,'unixepoch','localtime') as dt,
s.subject, a.address as sender, a.comment as name,
mb.url as mailbox, m.ROWID,
m.read, m.flagged, m.is_urgent, m.size, m.conversation_id,
m.automated_conversation, m.unsubscribe_type
FROM messages m
JOIN subjects s ON m.subject = s.ROWID
JOIN addresses a ON m.sender = a.ROWID
JOIN mailboxes mb ON m.mailbox = mb.ROWID
WHERE m.date_received >= ${SINCE}
AND m.deleted = 0
AND mb.url NOT LIKE '%Spam%' AND mb.url NOT LIKE '%Trash%'
AND mb.url NOT LIKE '%Junk%' AND mb.url NOT LIKE '%Sent%'
ORDER BY m.date_received DESC;" 2>/dev/nullStep 2: Score each email for priority
High priority signals (+points):
- is_urgent = 1: +10
- flagged = 1: +8
- read = 0: +3
- Subject contains: urgent, ASAP, action required, critical, deadline, review, approve: +5 each
- automated_conversation = 0 AND unsubscribe_type = 0 (likely real person): +4
- From work/EWS account: +2
- Large message (>50KB): +1 (likely real content)
- Subject contains reply indicators (RE:, FW:): +2
Low priority signals (−points):
- automated_conversation = 2 (bulk automated — newsletters, monitoring, CI/CD): −8
- unsubscribe_type > 0 (has List-Unsubscribe header — mailing list): −5
- Subject starts with PROBLEM:, OK:, ALARM:, CRIT: −8 (monitoring)
- Already read: −5
Compute a score per email, then bucket:
- Score ≥ 10: Critical
- Score 5–9: Important
- Score 1–4: Normal
- Score ≤ 0: Noise
Step 3: Read bodies for top-priority items
For Critical and Important emails (score ≥ 5):
python3 ~/.claude/skills/_mail-shared/parser.py <ROWID1> <ROWID2> ...Extract key info: what is being asked, any deadlines, any amounts.
Step 4: Check for conversation context
For unread replies, check if it's a continuation of a thread you started:
sqlite3 "$DB" "
SELECT COUNT(*) FROM messages m
JOIN mailboxes mb ON m.mailbox=mb.ROWID
WHERE m.conversation_id=<CONV_ID>
AND mb.url LIKE '%Sent%';" 2>/dev/nullIf you sent something in this thread → higher priority (someone replied to you).
Output Format
Critical — Act Now: [list with 1-line context from body]
Important — Handle Today: [list with subject and sender]
Normal — Read When Convenient: [count + brief list]
Noise (filtered): X emails [breakdown: Y monitoring alerts, Z newsletters, W CI/CD]
Total: X emails in window. Estimated action time: [estimate based on count]. Offer to read any specific email or start replying.
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
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.

