Email Triage
Reliable conversation-level email triage over a date range. Identifies genuinely open threads, emails that actually need a reply, and real correspondence hiding in junk — by reconstructing each conversation across inbox + sent + drafts + junk before judging, so mobile-quoted or already-sent replies are never mis-flagged. Use for "what's still open / what do I owe a reply / anything missed" over weeks or months.
Install
npx skills add Magnus-Gille/claude-skills --skill email-triagegit clone --depth 1 https://github.com/Magnus-Gille/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/email-triage ~/.claude/skills/email-triagePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# /email-triage — Reliable conversation-level email triage Account-to-CLI map and mail/calendar search rules: `~/repos/claude-config/docs/accounts.md`. `/check-email` is for quick inbox glances. **This skill is for trustworthy backlog triage** over a long window (weeks/months), where the cost of a wrong verdict is real (chasing a closed deal, missing a live one). ## The failure mode this skill exists to prevent Naive triage judges a thread from one message's `bodyPreview`. That is wrong because: - **Mobile replies roll into quoted text.** A reply Magnus sent from his phone often does *not* appear as a separate `sentitems` row in the window — it lives inside the quoted body of a later message. Judging by inbox rows alone makes resolved threads look open. - **The last *inbound* message is not the same as an open obligation.** Martin/Saab, Koenigsegg, William — all were flagged "needs Magnus" when Magnus had already replied (or the ball was explicitly in the other party's court). - **`bodyPreview` truncates before the resolution.** "Thanks for this — will get back within 1–2 weeks" reads as a question in preview; the closure is past the cutoff.
Details
- Skill name
email-triage- Repository
- Magnus-Gille/claude-skills
- Path
email-triage/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Email Triage skill do?
Reliable conversation-level email triage over a date range. Identifies genuinely open threads, emails that actually need a reply, and real correspondence hiding in junk — by reconstructing each conversation across inbox + sent + drafts + junk before judging, so mobile-quoted or already-sent replies are never mis-flagged. Use for "what's still open / what do I owe a reply / anything missed" over weeks or months.
How do I install the Email Triage skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add Magnus-Gille/claude-skills --skill email-triage. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Email Triage popular?
It lives in Magnus-Gille/claude-skills, which has 5 GitHub stars and 0 forks.
Related skills
Close
5Magnus-Gille/claude-skills
Close a coding-agent session or produce its final handoff only when the user explicitly asks to close, wrap up, or produce an end-of-session handoff.
Cloudflare Private Static Site
5Magnus-Gille/claude-skills
Create, preview, test, release, verify, or roll back a small static Cloudflare site protected by per-person HTTP Basic Auth. Use for private briefings, reports, one-pagers, document portals, or similar sites that should go from finished content to a custom domain in about ten minutes. Do not use for full applications or when the user requires SSO, identity lifecycle, or Cloudflare Access policy management.
Code Friction
5Magnus-Gille/claude-skills
Capture a small, opt-in set of concrete code-changeability observations during a coding task and hand them to Close without affecting readiness.
M5 Delegate
5Magnus-Gille/claude-skills
Delegate a self-contained task to Magnus's M5 when local inference is requested or the project's delegation policy applies.
Bun Streams
9jarle/bun-skills
Use Bun's streams API to work with binary data without loading it all into memory at once
Planning Tickets
5tomada1114/tomada-claude-plugins
Break requirements and design documents into GitHub Issues an implementing agent can ship without asking back: concrete values with their source, EARS requirements, explicit Not In Scope, machine-readable `Depends on #N` edges, a parallel-first breakdown, tracking parents with native sub-issues, and native blocked-by dependencies. Follows the repository's own issue conventions first — a triaging-issues skill's labels and body rules, a shipping-issues skill's ship contract — and falls back to its own templates only where the repository has none. Use when cutting tickets, breaking a feature or a
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.