# Triage Inbox

Triage academic email and calendar (Gmail / Google Calendar via the session's MCP) into...

- Repository: https://github.com/pedrohcgs/claude-code-my-workflow (1676 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-09-27
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add pedrohcgs/claude-code-my-workflow --skill triage-inbox -g -a claude-code -y`
Codex: `npx skills add pedrohcgs/claude-code-my-workflow --skill triage-inbox -g -a codex -y`
Cursor: `npx skills add pedrohcgs/claude-code-my-workflow --skill triage-inbox -g -a cursor -y`
Gemini CLI: `npx skills add pedrohcgs/claude-code-my-workflow --skill triage-inbox -g -a gemini-cli -y`

## Description

Triage academic email and calendar (Gmail / Google Calendar via the session's MCP) into a prioritized digest plus a referee-obligations tracker, classifying referee requests, R&R and editor correspondence, co-author threads, seminar and conference invites, and grant/admin deadlines, and proposing a human-gated action for each (draft reply, calendar hold, scaffold a project, snooze). Use when user says "triage my inbox", "check my academic email", "what needs my attention this week", "go through my mail", or when run as a scheduled routine. NEVER auto-sends or auto-accepts anything.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# /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`](../coauthor-brief/SKILL.md).
- To draft the R&R response document itself, that's [`/respond-to-referees`](../respond-to-referees/SKILL.md).

## Phases

The rest: https://github.com/pedrohcgs/claude-code-my-workflow/blob/HEAD/.claude/skills/triage-inbox/SKILL.md