What do I need to use Email Triage System?

The inbox state; The role's email reality; Past attempts.

Is Email Triage System free to use?

Yes — run it free in the browser playground (no API key needed for the sponsored trial, or bring any provider key), or install it into Claude Code, Cursor, ChatGPT and more via npx pm-claude-skills. MIT-licensed and open source.

Email Triage System

Q: How do I know the Email Triage System output is good?

The skill verifies itself against its own quality checks: Every message class in the backlog maps to exactly one verb; The two-minute rule is stated with its touch-it-once logic; Labels number ≤4 — structure stays under the complexity that killed the last system; The cadence is timeboxed and the between-windows rule is explicit.

🔵 Stable🕐 updated 2026-07-19 🔷 SkillSpec L3 pm-cowork

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.

▶ Run it free — no key needed 📝 Grade your existing draft View SKILL.md ↗

What to give it

▸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

✅ The bar it holds itself to

Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.

✓Every message class in the backlog maps to exactly one verb

✓The two-minute rule is stated with its touch-it-once logic

✓Labels number ≤4 — structure stays under the complexity that killed the last system

✓The cadence is timeboxed and the between-windows rule is explicit

✓30-day-plus backlogs get the bankruptcy option, framed as the rational move it is

⚠️ What it refuses to do

Do not build 20 folders — filing is procrastination that looks like organization

Do not leave actionable email in the inbox as its own reminder — task systems exist

Do not check between windows — ambient email is the tax that never stops

Do not process newest-first during backlog clearing — oldest-first or the backlog is immortal

Do not moralize the overflow — inboxes overflow structurally; the system is the fix, not discipline

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp

Related skills

🔌 Embed this skill

Drop this on your blog, docs, or site — it renders a "Run this skill" card:

<div data-pm-skill="email-triage-system"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

Email Triage System is one of 750 open-source professional AI agent skills — all SkillSpec L3. Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog