本文へ移動
cccskills
無料GitHub で公開

email-triage

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.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md4.2 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Master 1Password: vaults, Watchtower, passkeys, SSH agent, CLI, and family/team administration. Use when getting full value from 1Password personally or administering it for others.

日本語の概要は準備中です。原文の説明を表示しています。

aicodedecode/awesome-muse-skills172026年10月10日 更新

Create 3D visuals with modeling, texturing, lighting, rendering, and optimization for web and product.

日本語の概要は準備中です。原文の説明を表示しています。

aicodedecode/awesome-muse-skills172026年10月10日 更新

Create 3D web experiences: scene setup, models, materials, lighting, animation, scroll-driven scenes, and performance budgets. Use when adding 3D to websites beyond basic demos.

日本語の概要は準備中です。原文の説明を表示しています。

aicodedecode/awesome-muse-skills172026年10月10日 更新

Writing abstracts that get papers read — structured content, the 5-sentence core, and journal-specific constraints.

日本語の概要は準備中です。原文の説明を表示しています。

aicodedecode/awesome-muse-skills172026年10月10日 更新

Learn effectively from courses and academies: choosing programs, studying actively, and converting courses into skills. Use when investing time/money in structured learning.

日本語の概要は準備中です。原文の説明を表示しています。

aicodedecode/awesome-muse-skills172026年10月10日 更新

Audit designs for accessibility with WCAG checklists covering color, type, focus, motion, and content.

日本語の概要は準備中です。原文の説明を表示しています。

aicodedecode/awesome-muse-skills172026年10月10日 更新

aicodedecode のスキルをすべて見る

このスキルの問題を報告する