Email Triage GSuite

Your inbox pulls you in different directions. Important emails get buried under noise, promises you made slip through the cracks, and you can't tell at a glance what actually needs your response versus what's just sitting there read-but-unanswered. Without a system to track what you've committed to and what's waiting on you, items disappear into the background.

You get a daily or on-demand brief of what genuinely needs your attention — flagged by whether it contains an unanswered question from someone who matters, not by read status. The skill drafts reliable replies in your voice so you can send with one click, and remembers open items between runs so nothing disappears. You see your calendar tied to related open emails, and promises you made show up before they slip past their due date.

Surface what actually needs you and draft replies in your voice, with memory that carries items forward so nothing slips.

Requires Gmail, Google Calendar, and Google Drive connectors. On first run, the setup process in references/setup.md derives your triage config from your actual mail behavior. Config is stored in triage-config.md in a folder named 'Claude Email Triage' on your Drive. State files (one per run) are written to the same folder to track open items, mutes, and closures between runs.

Never sends mail — creates drafts only for your review Never deletes, archives, marks read, or reclassifies mail Never writes to calendar or shares Drive files Cannot write outside the skill's own memory folder on Drive Gmail read and draft creation only; Google Calendar read only; Google Drive read and write confined to memory folder Carried-over items reset if the memory folder is deleted or becomes inaccessible

This skill requires discipline around configuration — it guesses poorly at who matters until you guide it, and setup cannot be skipped. The brief only flags items from people and threads you've configured; if someone new emails you, they won't surface until their address is in config. Drafts are created but never sent, so you're responsible for the final review and click. If you have a task system somewhere else (Todoist, linear, etc.), this skill won't see delegations or tickets you've already made — it only reads what's in mail and calendar. The skill is opinionated: it refuses hard limits like never sending mail or writing to calendar, even if you ask directly. Finally, memory depends on Drive access; if the connector drops, memory becomes stale and items may repeat.