Email Inbox Zero System
Email is the task list other people write for you. Without a system you process it reactively, one message at a time, all day. The Email Inbox Zero System builds the triage rules, auto-filters, templates, and unsubscribe protocol that cut the time in half.
What this skill does
Most "inbox tips" advice is vague enough to be useless ("check email twice a day"). The reason inbox zero is hard isn't discipline — it's that there's no system filtering, archiving, and responding for you while you're not looking. This skill builds the actual system: triage rules, auto-filters that pre-sort before you open the inbox, templates that cover 80% of your replies, and a daily routine that batches the work into three short windows.
The triage is a four-bucket filter applied in five seconds per email. ACT — under two minutes, reply now. TASK — over two minutes, acknowledge, create a task, archive the email. TRACK — waiting on someone else, goes to a Waiting folder reviewed weekly. TRASH — archive immediately, build a filter so the next one doesn't even land in the inbox. Filters do the prep work before you arrive: newsletters skip the inbox, important senders get flagged, subjects matching "invoice / approval / review" land in a Needs Action label.
Templates are where most people save the most time. You get five generic categories (acknowledgment with timeline, declining a request, requesting information, meeting-request response, delegation) plus five more tailored to your specific recurring asks. The principle: 80% templated, 20% customised — which is faster than writing from scratch and better than a rushed personal reply with three typos. There's a 30-minute unsubscribe blitz protocol (search "unsubscribe", apply the 2-strike rule, build delete-filters for stubborn senders) that typically cuts daily volume by a third.
Two opinions worth flagging. The skill is explicit about Email Bankruptcy for backlogs over 1,000: archive everything, keep a safety-net Review folder, and start clean. If an email is 30 days old with no follow-up, it wasn't as important as it felt. And mobile email is read-only by default — thumb-typed replies are short, less thoughtful, and train senders to expect immediate response. Sub-two-minute approvals on mobile are fine; anything else waits for desktop.
When this triggers
- ·Your unread count is in four digits and you've quietly given up looking at most of it
- ·You spend the first hour of every morning in email and the work day feels like it starts at 11am
- ·You keep writing the same 'thanks, I'll have this by Friday' reply from scratch every time
- ·Newsletters are stacking up and you've never done a proper unsubscribe pass
- ·You manage a shared inbox (support@, info@) and emails are falling through the cracks
Example
Trigger
User: '3,400 unread, 80 a day incoming, drowning. Help.'
Output
Backlog protocol: Email Bankruptcy. 1. Search top 5 contacts last 14 days → "Review" folder 2. Search "urgent / deadline / overdue" last 30 days → "Review" 3. Select all remaining and archive. Yes, all of it. 4. Process "Review" using the 4-bucket filter below. 4-Bucket Filter (5 sec per email): · ACT (<2 min) — reply now · TASK (>2 min) — acknowledge + create task + archive · TRACK — move to Waiting folder, review weekly · TRASH — archive, build a filter for next time Auto-filters (4 to set up): · Newsletters → skip inbox, "Reference" label · Boss / top 3 clients → mark important · "invoice / approval / review" → "Needs Action" · Sent items with replies → "Follow-up" Templates: 5 generic + 5 customised to your recurring asks. Routine: 3 batches/day (~20 min total). No mobile replies except sub-2-min approvals.
Get this skill + 15 more
Included in the The Agency Owner Stack — scale delivery without scaling headcount. Save $130+ vs buying individually.
Get The Agency Owner Stack — $149What you get
- 275-line SKILL.md, ready to drop into ~/.claude/skills/
- Tested through 3 Karpathy-loop iterations (versions v1.0.0 → v1.3.0)
- Triggers automatically when relevant — no command to remember
- Lifetime updates as the skill is refined further
More from Project Management
Doesn't write teleprompter scripts — it writes structured talking outlines that make the speaker sound prepared, not robotic
Doesn't write internal status reports — it writes client-facing documents that manage expectations and build the relationship
Doesn't just format text — it filters for signal, highlight blockers early, and write updates that make managers confident without requiring follow-up questions
Doesn't just tell people to block time — it analyzes their role, energy patterns, and meeting load to engineer a schedule where deep work is structurally guaranteed, not aspirational
Doesn't just tell people to have fewer meetings — it classifies each specific meeting with a verdict and replacement strategy
Doesn't summarize meetings — it extracts the commitments that make meetings worth having
Browse the full library
297 skills across 31 categories. One purchase, lifetime updates.
See all bundles