/triage-inbox — Academic Inbox + Calendar Triage

Turn a noisy academic inbox into a short, decision-ready digest. Fetch recent mail and calendar context through the session's MCP servers (Gmail / Google Calendar), classify each thread into the categories an academic actually acts on, and propose one action per thread — always human-gated. The companion artifact is a running referee-obligations tracker so you never silently overcommit to reviews.

Core principle: this skill reads, classifies, and proposes. It drafts; it never sends, accepts, declines, or books anything without you. That boundary is what makes it safe to run unattended as a local Desktop scheduled task — not a cloud /schedule routine, whose fresh clone would lose the gitignored digest and tracker.

When to use

Weekly / daily sweep — "what landed that needs a decision?" without reading every thread yourself.
As a scheduled task — run each morning as a Desktop scheduled task (local), so the digest and the referee tracker stay on your machine; they are gitignored, so a cloud routine's fresh clone would neither see the tracker nor keep the digest. Because this skill is user-invoked, write the routine prompt as "Read .claude/skills/triage-inbox/SKILL.md and follow it" — a scheduled task cannot fire /triage-inbox by name.
Referee-load management — keep an honest count of outstanding reviews against a standing cap before you say yes to one more.
R&R / editor deadline capture — turn "minor revision due in 6 weeks" buried in an email into a calendar hold proposal.

When NOT to use

To actually send a reply, accept an invite, or book an event — this skill stops at proposals. You confirm and execute.
To handoff a project to a co-author — that's /coauthor-brief.
To draft the R&R response document itself — that's /respond-to-referees.