agentsclimarketplace

Inbox zero

Skill SkillMedev/skills/skills/inbox-zero

The open Skill Me catalog — every hosted skill as a portable, MIT-licensed SKILL.md

Install
npx -y skills add SkillMedev/skills --skill inbox-zero

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Processes any email backlog to zero using the 4Ds - Delete, Delegate, Defer, Do - with a mass-archive strategy for the obvious, a touch-each-email-once discipline, and a keep-it-clear system of batched processing windows, ruthless unsubscribing, filters, and a minimal folder setup. Use when someone says "I have 5,000 unread emails", "help me get to inbox zero", "email is eating my whole day", or treats their inbox as a to-do list. Do NOT use for drafting the reply emails themselves or prioritization rules for an ongoing support queue - use email-triage instead - or for protecting focus time around the email windows - use deep-work-planner instead.

SKILL.md

3.5 KB, 685 tokens by cl100k_base, as published. Nobody here has run it

Inbox Zero

Inbox Zero isn't an empty inbox for its own sake - it's a clear mind. The inbox is a processing queue, not a storage system or a to-do list. This skill clears it and keeps it clear.

The core idea

Your inbox should hold only unprocessed messages. Once you've looked at an email, it should not stay in the inbox - it gets a decision. Touch each email once.

The 4Ds

For every email, make one of four decisions immediately:

  • Delete (or Archive) - no action needed, no future reference. Most email is this. Be ruthless; you can always search archive later.
  • Delegate - someone else should own it. Forward with clear context and a deadline, then archive it from your inbox (track the handoff elsewhere if needed).
  • Defer - needs action but not now, or takes > 2 minutes. Move it to your task system or a "Today/This week" follow-up label, then archive. The action lives in your tasks, not your inbox.
  • Do - if it takes under 2 minutes, handle it right now, then archive. Deferring a 1-minute reply costs more than doing it.

Processing the backlog

  1. Sort by sender or subject to batch similar items.
  2. Mass-archive the obvious - newsletters, old notifications, threads already resolved. "Select all older than 30 days" is often safe to archive en masse.
  3. Process top to bottom, applying the 4Ds to each remaining message. No skipping back.
  4. Don't get pulled into deep work mid-processing - if a "Do" item balloons, make it a "Defer" and keep moving. Processing and doing are separate modes.

Keep it at zero

  • Batch your email - process in 2-3 fixed windows a day, not continuously. Turn off notifications between windows.
  • Unsubscribe relentlessly - every newsletter you don't read is recurring noise. Spend 10 minutes a week killing subscriptions.
  • Use filters/rules - auto-archive or label predictable senders (CI, receipts) so they skip the inbox.
  • Templates / canned responses for repeated replies.
  • One folder for archive - search beats foldering. Don't build elaborate folder trees.

Folder/label setup (minimal)

Inbox        -> unprocessed only
Archive      -> everything else (searchable)
Follow-up    -> waiting on someone / deferred actions (optional)

A simple daily routine

  • Morning window: process to zero, 4D each message.
  • Midday window: clear what arrived, fire off quick replies.
  • End of day: final pass to zero; deferred items already live in your task list.

Anti-patterns

  • Treating the inbox as a to-do list - it has no priority, no due dates, and others fill it.
  • Reading an email and leaving it unread "to deal with later" - you'll touch it 5 times.
  • Checking email constantly - it shatters focus; batch it.
  • Building 40 folders - you'll spend more time filing than searching.

Gives 0 of the 12 instructions most roadmap strategy skills give in 685 tokens

Counted across 591 of the 672 authors here whose files we hold, read 2026-08-06

  • read product marketing context before asking questionsin 21 of 591, across 10 files
  • base price on perceived value, not costin 15 of 591, across 4 files
  • compact after finalizing a planin 14 of 591, across 9 files
  • differentiate tiers using features, limits, or supportin 14 of 591, across 3 files
  • use Van Westendorp to find acceptable price rangein 13 of 591, across 2 files
  • use MaxDiff to identify highly valued featuresin 13 of 591, across 2 files
  • map topics to buyer journey stagesin 12 of 591, across 6 files
  • Extract domain capabilities and classify subdomainsin 11 of 591, across 1 file
  • Define bounded contexts around consistency and ownershipin 11 of 591, across 1 file
  • Establish a ubiquitous language glossary and anti-termsin 11 of 591, across 1 file
  • Capture context boundaries in ADRs before implementationin 11 of 591, across 1 file
  • Open the strategic design template if neededin 11 of 591, across 1 file

Said here and by no other author read

  • treat the inbox as a processing queue
  • touch each email exactly once
  • apply the 4Ds to every email
  • archive items older than 30 days en masse
  • process emails top to bottom
  • separate processing mode from doing mode

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.