Agent skill · Content & Marketing

email-triage-system

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.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill email-triage-system --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/email-triage-system/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 1.

What's inside
Steps it walks through
  1. What This Skill Produces
  2. Required Inputs
  3. Framework: The Four Verbs
  4. Output Format
  5. The Backlog Pass
  6. The Rules Card (keep visible)
  7. The Cadence
  8. Quality Checks
  9. Anti-Patterns
More from pm-claude-skills
All skills →
About this skill
What does the email-triage-system skill do?

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.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill email-triage-system --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going