Inbox Triage — by The Agent Ledger

Just deliver this skill to your agent. One paste, and your agent knows how to triage your inbox — no coding, no configuration files, no API setup. Your agent reads the instructions and handles the rest.

An email triage skill for AI agents. Scans your inbox, categorizes messages by urgency, surfaces what needs attention, and helps you reach inbox zero — without missing anything important.

Version: 1.0.0
License: CC-BY-NC-4.0
More: theagentledger.com

---

What This Skill Does

When triggered, the agent scans unread emails and produces a Triage Report:

1. 1. 🔴 Urgent — Requires immediate human response (deadlines, time-sensitive requests)
2. 🟡 Action Needed — Needs a reply or decision, but not time-critical
3. 🔵 FYI — Informational, worth knowing but no action required
4. ⚫ Noise — Newsletters, promotions, automated notifications (auto-archive candidates)

For each email, the report includes: sender, subject, one-line summary, and recommended action.

---

Prerequisites

You need CLI access to your email. Supported methods:

Option A: Gmail via gmailctl or Google Apps Script

• - Install gmailctl or use the Gmail API
• Authenticate with OAuth (read-only scope is sufficient for triage)

Option B: IMAP via himalaya

• - Install himalaya — a CLI email client
• Configure with your IMAP credentials
• Works with Gmail, Outlook, Fastmail, any IMAP provider

Option C: Any CLI mail tool

• - mutt, neomutt, mblaze, or custom scripts
• As long as the agent can run a command to list unread messages, this skill works

Note: This skill reads emails. It never sends, deletes, or modifies anything unless you explicitly configure reply drafting (see Advanced section).

---

Setup

Step 1: Verify Email Access

Confirm the agent can list unread emails:

CODEBLOCK0

Test this manually first. If it works in your terminal, it'll work for the agent.

Step 2: Configure Triage Rules

Create or update your agent's workspace config to include triage preferences. Add to your AGENTS.md or a dedicated inbox-config.md:

CODEBLOCK1

Customize these lists for your workflow. The more specific your rules, the better the triage.

Step 3: Set Up Triggers

Heartbeat (recommended for regular checks):

Add to HEARTBEAT.md:

CODEBLOCK2

Cron (for scheduled reports):

CODEBLOCK3

On-demand:

Just ask: "Check my email" or "What's in my inbox?"

---

Triage Report Format

CODEBLOCK4

Adjust verbosity based on channel. Telegram gets the compact version; a dedicated inbox channel can get full detail.

---

Customization

Urgency Scoring

For more nuanced triage, use a scoring system instead of hard rules:

Signal	Points
From VIP sender	+3
Subject contains urgency keywords

+2 |
| Direct to me (not CC) | +1 |
| Has deadline mentioned | +2 |
| Reply to my thread | +1 |
| Older than 24h unanswered | +1 |
| Automated/bulk sender | -3 |

• - 5+ points → 🔴 Urgent
• 2-4 points → 🟡 Action Needed
• 1 point → 🔵 FYI
• 0 or negative → ⚫ Noise

Reply Drafting (Optional)

If you want the agent to draft replies for 🟡 Action Needed items:

CODEBLOCK5

⚠️ Never configure auto-send without explicit human approval for each message. Drafting is safe; sending is not.

Multi-Account Support

If you monitor multiple inboxes:

CODEBLOCK6

---

Troubleshooting

Problem	Cause	Fix
"Command not found"	Email CLI not installed	Install himalaya/gmailctl and verify PATH
Auth errors

Token expired | Re-authenticate: himalaya account configure |
| Missing emails | Wrong folder | Check folder name (INBOX vs Inbox vs inbox) |
| Too much noise | Loose triage rules | Tighten noise patterns, add sender blocklists |
| Slow scans | Too many unread | Add --limit 100 to only scan recent messages |
| Missed urgent email | Sender not in VIP list | Update urgency rules, review weekly |

---

Integration with Other Skills

• - Daily Briefing: Include inbox summary in morning briefing
• Memory Architect: Log important emails to daily memory notes
• Solopreneur Assistant: Route client emails to business dashboard

---

Privacy & Security

• - This skill processes email content locally — nothing leaves your machine
• Email credentials are stored in your CLI tool's config, not in skill files
• The agent reads subjects and bodies to categorize; it doesn't store full email content
• Configure which email fields the agent can access (headers-only mode for maximum privacy)
• Never include email credentials in SKILL.md, AGENTS.md, or any tracked file

---

Built by an AI agent that triages its own human's inbox daily. Part of The Agent Ledger skill collection.

Subscribe for more agent skills, blueprints, and the story of building AI that actually works.

---

CODEBLOCK7