Email Triage System Skill
Inboxes overflow because every message gets the same treatment: opened, half-read, left "for later" — and later compounds. Triage replaces reading with deciding: every message gets exactly one of four verbs on first touch, the two-minute rule handles the small stuff instantly, and the system runs on a cadence measured in minutes per day, not heroic weekend purges.
What This Skill Produces
- The triage pass — the current backlog sorted into the four verbs, oldest-first batches
- The four-verb rules — archive / reply-now / task / park, with the decision test for each
- The minimal structure — 3–4 labels maximum; folders are where email goes to die
- The daily cadence — two fixed windows, timeboxed, with the backlog-never-returns rule
Required Inputs
Ask for these if not provided:
- The inbox state — count, oldest unread, and the honest description ("4,000, mostly newsletters" vs. "200, mostly real")
- The role's email reality — customer-facing (reply SLAs matter) vs. internal (batching is fine)
- Past attempts — what system died before and why; the new one must not repeat its failure mode
Framework: The Four Verbs
- Archive (the default): no action needed, might need finding later → archive immediately. Search beats filing; the archive is one big searchable bucket. Most email is this, and treating it as anything else is the whole problem.
- Reply-now (the two-minute rule): if a real reply takes under two minutes, send it during triage — touching it twice costs more than answering it once. Short is fine; sent beats polished.
- Task: replies needing real work become tasks in the task system with the email linked — never left in the inbox as their own reminder. An inbox used as a to-do list fails at both jobs.
- Park (rare, explicit): genuinely waiting-on-something messages get a
@waiting label and a weekly review. Parking without the review label is just procrastination with a name.
- The cadence: two triage windows daily (morning, late afternoon), 15–20 minutes each, inbox to zero decisions (not zero work). Between windows, email stays closed — every glance costs a context switch. Backlogs older than 30 days get declared bankrupt: archive-all + one "if it was important, resend" note to self.
Output Format
Email Triage: [inbox state] → system
The Backlog Pass
[Batches with verb counts: "archive ~3,100 (newsletters, notifications) · reply-now 12 · task 23 · park 4" · the bankruptcy call if warranted]
The Rules Card (keep visible)
[The four verbs with their tests · the two-minute rule · labels: @waiting, @task-filed, +1 optional]
The Cadence
[Windows, lengths, the closed-between rule · the weekly @waiting review]
Quality Checks
Anti-Patterns
1---2name: email-triage-system-23description: "Turn an overflowing inbox into a four-verb system — archive, reply-now, task, or park — with the two-minute rule enforced and a daily cadence that survives busy weeks. Use when asked help me get to inbox zero, my email is out of control, build me an email triage system, or process this backlog. Produces the triage pass on the actual inbox, the four-verb rules, the folder/label minimal set, and the daily cadence."4homepage: https://mohitagw15856.github.io/pm-claude-skills/skill/email-triage-system.html5metadata:6 source: https://skillmd.com/skills/mohitagw15856/email-triage-system-27 openclaw:8 emoji: 🧠9---1011# Email Triage System Skill1213Inboxes overflow because every message gets the same treatment: opened, half-read, left "for later" — and later compounds. Triage replaces reading with *deciding*: every message gets exactly one of four verbs on first touch, the two-minute rule handles the small stuff instantly, and the system runs on a cadence measured in minutes per day, not heroic weekend purges.1415## What This Skill Produces1617- **The triage pass** — the current backlog sorted into the four verbs, oldest-first batches18- **The four-verb rules** — archive / reply-now / task / park, with the decision test for each19- **The minimal structure** — 3–4 labels maximum; folders are where email goes to die20- **The daily cadence** — two fixed windows, timeboxed, with the backlog-never-returns rule2122## Required Inputs2324Ask for these if not provided:25- **The inbox state** — count, oldest unread, and the honest description ("4,000, mostly newsletters" vs. "200, mostly real")26- **The role's email reality** — customer-facing (reply SLAs matter) vs. internal (batching is fine)27- **Past attempts** — what system died before and why; the new one must not repeat its failure mode2829## Framework: The Four Verbs30311. **Archive (the default):** no action needed, might need finding later → archive immediately. Search beats filing; the archive is one big searchable bucket. Most email is this, and treating it as anything else is the whole problem.322. **Reply-now (the two-minute rule):** if a real reply takes under two minutes, send it during triage — touching it twice costs more than answering it once. Short is fine; sent beats polished.333. **Task:** replies needing real work become tasks in the task system with the email linked — *never* left in the inbox as their own reminder. An inbox used as a to-do list fails at both jobs.344. **Park (rare, explicit):** genuinely waiting-on-something messages get a `@waiting` label and a weekly review. Parking without the review label is just procrastination with a name.355. **The cadence:** two triage windows daily (morning, late afternoon), 15–20 minutes each, inbox to zero *decisions* (not zero work). Between windows, email stays closed — every glance costs a context switch. Backlogs older than 30 days get declared bankrupt: archive-all + one "if it was important, resend" note to self.3637## Output Format3839# Email Triage: [inbox state] → system4041## The Backlog Pass42[Batches with verb counts: "archive ~3,100 (newsletters, notifications) · reply-now 12 · task 23 · park 4" · the bankruptcy call if warranted]4344## The Rules Card (keep visible)45[The four verbs with their tests · the two-minute rule · labels: @waiting, @task-filed, +1 optional]4647## The Cadence48[Windows, lengths, the closed-between rule · the weekly @waiting review]4950## Quality Checks5152- [ ] Every message class in the backlog maps to exactly one verb53- [ ] The two-minute rule is stated with its touch-it-once logic54- [ ] Labels number ≤4 — structure stays under the complexity that killed the last system55- [ ] The cadence is timeboxed and the between-windows rule is explicit56- [ ] 30-day-plus backlogs get the bankruptcy option, framed as the rational move it is5758## Anti-Patterns5960- [ ] Do not build 20 folders — filing is procrastination that looks like organization61- [ ] Do not leave actionable email in the inbox as its own reminder — task systems exist62- [ ] Do not check between windows — ambient email is the tax that never stops63- [ ] Do not process newest-first during backlog clearing — oldest-first or the backlog is immortal64- [ ] Do not moralize the overflow — inboxes overflow structurally; the system is the fix, not discipline