Skip to content

borghei/Claude-Skills / personal-productivity/email-triage

email-triage

Verified

Classify a batch of emails into action categories (reply now, reply later, archive, delete, unsubscribe) and surface unsubscribe candidates. Use after a busy week, running inbox zero, or triaging email overload.

FileKindSize
SKILL.mdskill md5.2 KB
assets/gmail_filter_template.mdmarkdown2.3 KB
references/inbox_zero_method.mdmarkdown3.7 KB
scripts/email_classifier.pyscript6.4 KB

references/inbox_zero_method.md

View on GitHub
# Inbox Zero Method

Inbox Zero (Merlin Mann's coinage, c. 2007) is *not* about having zero unread emails — it's about treating email as something you process to a decision rather than a constant ambient stream. The goal is **zero attention given to email outside processing windows**.

---

## The Five Decisions

When processing an email, pick one of five actions immediately:

1. **Delete** — no future value
2. **Delegate** — forward to someone better-positioned, with explicit ask
3. **Defer** — needs more time; move to a follow-up folder with a date
4. **Do** — if it takes < 2 minutes, do it now
5. **File** — informational; archive with the right label

The key word is **immediately** — not "I'll think about it later" or "let me reread this."

---

## Daily Routine

**Morning processing window (15 min):**
- Process new email from overnight using the five decisions
- Reply to anything < 2 minutes
- Move longer items to "today" or "this week"

**Mid-day window (15 min):**
- Process new email since morning
- Same five decisions

**End-of-day window (10 min):**
- Final pass; defer anything not handled to tomorrow's "today" folder
- Inbox should be at zero by end of day

**Outside windows:** email closed. Notifications off.

---

## Folder Structure

Minimum:
- **Inbox** — incoming only
- **Today** — items to handle today
- **This week** — items to handle this week
- **Waiting** — sent emails waiting for reply
- **Archive** — everything else (one big bucket — search is faster than folders)

Avoid: nested folder hierarchies. Search is faster than the cognitive cost of where-does-this-go decisions.

---

## Email That Shouldn't Be Email

If a message is a meeting → put it on the calendar
If a message is a task → put it in your task tool
If a message is a document → store the document, not the email
If a message is a long discussion → move to the discussion tool (Slack, Notion, etc.)

The most-skipped insight in inbox-zero practice: **email is a transport, not a storage system**. Move things out.

---

## Common Pitfalls

- **Reading email more than processing it.** Each open without a decision is a tax on attention.
- **"Unread" as a to-do list.** Unread doesn't mean undone. Use a real task tool.
- **Folder over-engineering.** Three folders work; thirty don't.
- **Forwarding without context.** Delegations should include the action you want and the deadline.
- **Reply-all reflex.** Default to reply-to-sender; reply-all only when others actively need to know.
- **Slow unsubscribe.** Marketing senders compound. One unsubscribe today saves dozens of decisions next year.
- **Starring everything.** A star on every email = stars on nothing.

---

## When Inbox Zero Doesn't Work

- **High-volume support inboxes** — these need a ticketing system, not personal inbox-zero discipline.
- **Shared inboxes** — these need a collaboration model (assignments, owner per item).
- **Roles where email is the work** — recruiters, sales, account managers may need a different system entirely (CRM-driven inbox).

For most other roles, inbox-zero practice scales from 10 to 200+ emails/day with the same routine.

---

## Bootstrap (One-Time)

If you're starting from a 5,000-message inbox:

1. Move everything older than 30 days → archive (you'll find 1% later via search; the rest you would never have looked at again)
2. Triage the remaining ~500 with the classifier from this skill
3. Adopt the daily routine going forward

You don't need to read 5,000 emails. You need to be at zero tomorrow morning and stay there.

---

## Resources

- Merlin Mann's original posts (43folders.com, archived)
- David Allen's *Getting Things Done* — the underlying methodology
- Cal Newport's *A World Without Email* — the deeper critique
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall