name: gmail-inbox-triage description: Triage a Gmail inbox into actionable buckets such as urgent, needs reply soon, waiting, and FYI using connected Gmail data. Use when the user asks to triage the inbox, rank what needs attention, find what still needs a reply, or separate important mail from noise.
Gmail Inbox Triage
Overview
Use this skill for direct inbox-triage requests. Build on the core Gmail skill at ../gmail/SKILL.md, especially its search and thread-reading guidance.
Workflow
- Default to
INBOXand a clear timeframe unless the user asks for a broader audit. - Use
search_emailsto build a shortlist before reading bodies. - Exclude obvious noise early if newsletters, calendar churn, or automated alerts dominate the first pass.
- Use
batch_read_emailonly when snippets are not enough to classify urgency or reply-needed status. - Escalate to
read_email_threadwhen a message appears to be part of an active conversation and the surrounding thread may change the classification. Be careful because low-signal notifications can turn into long threads;read_email_threadexposestotal_messages, which helps detect that. - Return the result in explicit Inbox Zero-style buckets such as
Urgent,Needs reply soon,Waiting, andFYI.
Bucket Heuristics
Urgent: direct asks with time pressure, blocking messages, decision requests with deadlines, or operational mail that can break if ignored.Needs reply soon: direct asks without same-day urgency, active conversations where the user is the next responder, or follow-ups that will go stale if ignored.Waiting: threads where the user already replied or the current blocker belongs to someone else.FYI: announcements, newsletters, calendar churn, and transactional mail that does not require action.
Output
- Include sender, subject, why each item is in its bucket, and the likely next action.
- State timeframe, search scope, and confidence.
- Treat reply-needed as an inference, not a guaranteed state.
- Avoid claiming the inbox is fully triaged if you only checked a narrow slice.