New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Email Triage System

by mohitagw15856 in mohitagw15856/pm-claude-skills

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.

MITAuto-check passedProductivity & Automation

Install Email Triage System

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill email-triage-system -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills email-triage-system --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/email-triage-system .claude/skills/email-triage-system && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
email-triage-system
GitHub stars
1.4k
Token cost
~1.1k tokens
SKILL.md length
564 words
Files
1
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

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.

  • Works in 5 steps: Archive (the default): no action needed,… → Reply-now (the two-minute rule): if a… → Task: replies needing real work become… → …
  • Asked help me get to inbox zero
  • SKILL.md covers What This Skill Produces, Required Inputs, Framework: The Four Verbs and Output Format, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Email Triage System is an agent skill from mohitagw15856/pm-claude-skills. 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.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Productivity & Automation, covering Email management. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.

When your agent uses it

  • Asked help me get to inbox zero
  • My email is out of control
  • Build me an email triage system
  • Process this backlog

Example prompts

  • “/email-triage-system”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Archive (the default): no action needed, might need finding later → archive immediately. Search beats filing; the archive is one big…
  2. Reply-now (the two-minute rule): if a real reply takes under two minutes, send it during triage — touching it twice costs more than…
  3. Task: replies needing real work become tasks in the task system with the email linked — never left in the inbox as their own reminder. An…
  4. Park (rare, explicit): genuinely waiting-on-something messages get a @waiting label and a weekly review. Parking without the review label…
  5. The cadence: two triage windows daily (morning, late afternoon), 15–20 minutes each, inbox to zero decisions (not zero work). Between…

What it can do on your machine

Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Email Triage System loads about 1.1k tokens when it runs. Until then it costs about 109 tokens; SKILL.md has 564 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~109
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 564 words, ~1,071 tokens.

Download SKILL.mdSave it as .claude/skills/email-triage-system/SKILL.md (or your agent's skills folder).
name
email-triage-system
description
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.

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. Archive (the default): no action needed, might need finding later → archive immediately. Search beats filing; the archive is one big searchable bucket. Most email is this, and treating it as anything else is the whole problem.
  2. Reply-now (the two-minute rule): if a real reply takes under two minutes, send it during triage — touching it twice costs more than answering it once. Short is fine; sent beats polished.
  3. Task: replies needing real work become tasks in the task system with the email linked — never left in the inbox as their own reminder. An inbox used as a to-do list fails at both jobs.
  4. Park (rare, explicit): genuinely waiting-on-something messages get a @waiting label and a weekly review. Parking without the review label is just procrastination with a name.
  5. The cadence: two triage windows daily (morning, late afternoon), 15–20 minutes each, inbox to zero decisions (not zero work). Between windows, email stays closed — every glance costs a context switch. Backlogs older than 30 days get declared bankrupt: archive-all + one "if it was important, resend" note to self.
Show full SKILL.md (210 more words)Show less

Output Format

Email Triage: [inbox state] → system

The Backlog Pass

[Batches with verb counts: "archive ~3,100 (newsletters, notifications) · reply-now 12 · task 23 · park 4" · the bankruptcy call if warranted]

The Rules Card (keep visible)

[The four verbs with their tests · the two-minute rule · labels: @waiting, @task-filed, +1 optional]

The Cadence

[Windows, lengths, the closed-between rule · the weekly @waiting review]

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
  • 30-day-plus backlogs get the bankruptcy option, framed as the rational move it is

Anti-Patterns

  • 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

Example Trigger Phrases

  • "Help me get to inbox zero."
  • "My email is out of control."
  • "Build me an email triage system."
  • "Process this backlog."

© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/email-triage-system of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

Email Triage System next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Email Triage System compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Email Triage System this skillmohitagw15856/pm-claude-skills1.4k—~1.1kAutomated safety check: PassMIT
Garden Inboxpaperclipai/paperclip100k—~1.1kAutomated safety check: PassMIT
Continuetelegramdesktop/tdesktop33k2 repos~9.4kAutomated safety check: PassGPL-3.0
Process Inboxtelegramdesktop/tdesktop33k1 repos~5.4kAutomated safety check: PassGPL-3.0
Process InboxTDesktop-x64/tdesktop3k—~4.3kAutomated safety check: PassGPL-3.0
Career-Ops Gmail Lead Plugincareer-ops-hq/career-ops74k—~233Automated safety check: NotesMIT

Similar skills

  • Garden Inbox

    paperclipai/paperclip

    Scan a Paperclip user's Mine inbox, classify reversible archive candidates, request checkbox confirmation, and archive only accepted selections.

    100k GitHub stars~1.1k tokensUpdated today
    Productivity & AutomationAuto-check passed

  • Continue

    telegramdesktop/tdesktop

    Continue autonomous Telegram Desktop development from the shared ai-tdesktop repository.

    33k GitHub starsUsed in 2 repos~9.4k tokens
    Productivity & AutomationAuto-check passed

  • Process Inbox

    telegramdesktop/tdesktop

    Process the local ignored ai-tdesktop inbox into durable, independently testable Telegram Desktop task records while task execution worktrees remain active.

    33k GitHub starsUsed in 1 repo~5.4k tokens
    Productivity & AutomationAuto-check passed

  • Process Inbox

    TDesktop-x64/tdesktop

    Process the local ignored ai-tdesktop inbox into durable, independently testable Telegram Desktop task records while task execution worktrees remain active.

    3k GitHub stars~4.3k tokensUpdated 19 days ago
    Productivity & AutomationAuto-check passed

  • Career-Ops Gmail Lead Plugin

    career-ops-hq/career-ops

    Pulls job leads from a Gmail label into the career-ops pipeline, extracting job URLs from DMARC-passing emails and de-duplicating against existing leads.

    74k GitHub stars~233 tokensUpdated today
    Productivity & AutomationAuto-check: notes

  • Atomicmail

    Atomic-Mail/atomic-mail-agentic

    Read and write email through the Atomic Mail from an AI agent.

    266 GitHub starsUsed in 1 repo~2k tokens
    Productivity & AutomationAuto-check passed

More from mohitagw15856/pm-claude-skills

All 1,348 skills in this repo

  • Car Tco

    mohitagw15856/pm-claude-skills

    Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed

  • Cs Health Scorecard

    mohitagw15856/pm-claude-skills

    Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~2.4k tokensUpdated 2 days ago
    Auto-check passed

  • Exit Waterfall

    mohitagw15856/pm-claude-skills

    Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed

  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated 2 days ago
    Auto-check passed

  • Fire Number

    mohitagw15856/pm-claude-skills

    Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed

  • Freelance Rate

    mohitagw15856/pm-claude-skills

    Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.

    1.4k GitHub stars~1.2k tokensUpdated 2 days ago
    Auto-check passed

Categories

Questions about Email Triage System

What does Email Triage System 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. Email Triage System is an agent skill from mohitagw15856/pm-claude-skills. 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.

When should I use Email Triage System?

Email Triage System fits situations like: asked help me get to inbox zero; my email is out of control; build me an email triage system; process this backlog.

How do I install Email Triage System in Claude Code?

Run `npx skills add mohitagw15856/pm-claude-skills --skill email-triage-system -a claude-code`. Or copy the skill folder (skills/email-triage-system in mohitagw15856/pm-claude-skills) into .claude/skills/email-triage-system in your project. Claude Code loads it when a task matches its description.

How do I install Email Triage System in Codex?

Run `npx skills add mohitagw15856/pm-claude-skills --skill email-triage-system -a codex`. Or copy the skill folder (skills/email-triage-system in mohitagw15856/pm-claude-skills) into .agents/skills/email-triage-system in your project. Codex loads it when a task matches its description.

Can I use Email Triage System in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill email-triage-system -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/email-triage-system, .gemini/skills/email-triage-system, .github/skills/email-triage-system and .opencode/skills/email-triage-system in your project.

What does Email Triage System need to run?

SKILL.md names no scripts, command-line tools or credentials: Email Triage System is instructions for the agent only.

Does Email Triage System access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Email Triage System safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Email Triage System use?

Email Triage System is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Email Triage System use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Email Triage System?

Skills that share tags, products or a category with Email Triage System: Garden Inbox (paperclipai/paperclip, 100k stars), Continue (telegramdesktop/tdesktop, 33k stars), Process Inbox (telegramdesktop/tdesktop, 33k stars) and Process Inbox (TDesktop-x64/tdesktop, 3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Email Triage System?

mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.

Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.