AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Mail Triage

skill-aashari-ai-agent-skills-mail-triage · by aashari

>-

No reviews yet
0 installs
21 views
0.0% view→install

Install

$ agentstack add skill-aashari-ai-agent-skills-mail-triage

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-aashari-ai-agent-skills-mail-triage)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
5mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Mail Triage? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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/null

Step 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
  • automatedconversation = 0 AND unsubscribetype = 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   ...

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=
  AND mb.url LIKE '%Sent%';" 2>/dev/null

If 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.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.