Skip to content
Back to skills

Email Triage

ASecurity

Reach and sustain inbox zero: triage workflows, filters, templates, batching, and unsubscribing systems. Use when email eats your day or your inbox has become an anxiety source.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 29, 2026
ai-agentsrustgoreact

Works with

  • cli

Security analysis

A100/100

Scanned September 29, 2026

npx -y skills add aicodedecode/awesome-muse-skills --skill email-triage --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Email Triage?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Email Triage
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-email-triage/badge)](https://www.skillsdirectory.com/skills/aicodedecode-email-triage)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: email-triage
description: Reach and sustain inbox zero: triage workflows, filters, templates, batching, and unsubscribing systems. Use when email eats your day or your inbox has become an anxiety source.
category: productivity
---

# Email Triage

## Overview

Email is other people's priorities arriving on their schedule. Triage = processing it fast, on your schedule.

Core loop: batch processing, one-touch decisions (delete, delegate, do, defer), and reducing volume at the source.

Inbox zero isn't permanent emptiness — it's a regularly emptied inbox plus a trusted process.

Most 'email problems' are volume and boundary problems, not speed problems. Fix the source first.

## When to use

- Inbox has hundreds or thousands of unread messages
- Email interrupts deep work constantly (always open, notifications on)
- Setting up email for a new role or team
- Designing team email norms (response times, CC rules, channel choice)
- Digging out from a backlog after leave or a crunch period

## Core concepts

- **The 4 D's.**
  Per message, decide once: Delete/archive, Delegate (forward + clear ask + date), Do (<2-5 min: reply now), Defer (task with date, then archive).
- **Batching.**
  2-4 scheduled blocks daily (e.g., 9:00, 13:00, 16:30). Outside blocks: inbox closed, notifications off. Nothing needs a 3-minute response.
- **Filters and rules.**
  Auto-file newsletters, notifications, receipts, alerts into labels that skip the inbox. Inbox = only mail needing your decision.
- **Templates and snippets.**
  Canned replies for meeting requests, intros, declines, follow-ups. Text expander makes them instant. Typed twice a week? Template it.
- **Unsubscribe ruthlessly.**
  Every newsletter must continuously earn its place. Unopened last five? Unsubscribe. Keepers go to a read-later service.
- **Response-time norms.**
  Communicate: same-day for truly urgent, 24-48h otherwise. Fast replies train faster expectations — calm norms help everyone.
- **Right channel.**
  Email = non-urgent + documented. Urgent -> call/chat. Discussion -> meeting/thread. Say 'no reply needed' on FYIs.
- **Archive + search.**
  Search beats filing. A handful of active folders max; archive everything processed.

## Practical workflow

1. **Declare bankruptcy if needed.**
   Over ~1,000 unread? Archive everything older than 30 days. If important, they'll follow up. Start clean.
2. **Set up filters first.**
   Rules for noise — label, skip inbox. Do this before the backlog, or it regrows while you work.
3. **Unsubscribe sprint.**
   20 focused minutes killing non-essential subscriptions. Daily dividends forever.
4. **Process the backlog in sprints.**
   Oldest to newest, 4 D's each, 25-min sprints. Target: zero (or <20) within a few sessions.
5. **Install batching.**
   2-4 email blocks on the calendar. Notifications off everywhere. Tell key people the genuine-urgency channel.
6. **Build templates.**
   Your 5-10 most common replies as templates/snippets. Consistency + speed.
7. **Maintain weekly.**
   Friday 15-min sweep: process to zero, check filters for misfiles, unsubscribe from one more thing.
8. **Set an email signature.**
   Include response-time expectations. It pre-trains senders and gives you cover for batching.

## Common pitfalls

- **Living in the inbox.**
  Always open 'just in case.' Every check costs 5-15 min of refocus even when empty. Batch or bleed.
- **Inbox as task list.**
  200 messages = 200 unmade decisions. Actionable mail becomes dated tasks, then leaves the inbox.
- **Reply-all and CC bloat.**
  Reply-all by default trains everyone to ignore you. Owner in To, rest in CC, FYI blasts in BCC.
- **Over-long replies.**
  Most need 2-5 sentences. Long mail gets skimmed or deferred. Brief; offer a call for complexity.
- **No unsubscribe discipline.**
  'Read later' for 50 newsletters = 50 daily micro-decisions. Unsubscribe; search finds it if ever needed.
- **Instant-response expectation.**
  2-minute replies train 2-minute expectations forever. A calm 24h norm is healthier for all.
- **Checking email first thing.**
  Starting in others' priorities guarantees a reactive day. Your plan first, email second.
- **Folders as procrastination.**
  Elaborate taxonomies where mail goes to be forgotten. Archive + search wins 95% of the time.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…