What do I need to use Email Triage?

Time window (optional); Always-include senders (optional); Always-ignore senders (optional); Focus area (optional).

Is Email Triage 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

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

The skill verifies itself against its own quality checks: Time window was applied correctly — no emails outside the window are included; Gmail connector was confirmed active before reading; Every High Priority email has a specific, concrete "What they need" sentence — not a vague summary; Reply starters match the tone of the original email (formal/informal).

🟡 Experimental🕐 updated 2026-06-24 🔷 SkillSpec L3 pm-operations

Triage a Gmail inbox down to only what needs you. Use when asked to triage email, clear an inbox, find what needs a reply, or summarise recent mail. Produces a prioritised list of items needing action — replies, decisions, follow-ups — for a configurable window (default last 8 hours), filtering out receipts, notifications, and newsletters.

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

🗣 Say this to your agent

“`/email-triage`”“Check my emails”“What emails need my attention?”“Triage my inbox for the last 8 hours”“What came in since this morning?”

What to give it

▸Time window (optional) — Last 8 hours

▸Always-include senders (optional) — None

▸Always-ignore senders (optional) — None

▸Focus area (optional) — None

✅ 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.

✓Time window was applied correctly — no emails outside the window are included

✓Gmail connector was confirmed active before reading

✓Every High Priority email has a specific, concrete "What they need" sentence — not a vague summary

✓Reply starters match the tone of the original email (formal/informal)

✓Filtered-out count is accurate and broken down by category

✓FYI section contains only emails with no action required — nothing actionable is buried here

✓Always-include senders surfaced regardless of category

✓Always-ignore senders/domains are fully suppressed

⚠️ What it refuses to do

Do not surface FYI emails in the High or Medium priority sections — burying actionable items with informational ones defeats the purpose of triage

Do not write vague "What they need" summaries ("Sarah sent an email about the report") — every summary must state the actual ask, not a description of the email

Do not apply the same tone to every reply starter — a formal email from a client requires a different opener than a casual Slack-style email from a colleague

Do not include emails outside the requested time window — time window accuracy is the core trust signal for this skill

Do not omit the filtered-out count — users need to know how much was scanned, not just what was surfaced, to trust the triage is complete

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

Start with

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"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

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