gmail-inbox-triage
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.
Best use case
gmail-inbox-triage is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using gmail-inbox-triage should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/gmail-inbox-triage/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How gmail-inbox-triage Compares
| Feature / Agent | gmail-inbox-triage | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Gmail Inbox Triage ## Overview Use this skill for direct inbox-triage requests. Build on the core Gmail skill at [../gmail/SKILL.md](../gmail/SKILL.md), especially its search and thread-reading guidance. ## Workflow 1. Default to `INBOX` and a clear timeframe unless the user asks for a broader audit. 2. Use `search_emails` to build a shortlist before reading bodies. 3. Exclude obvious noise early if newsletters, calendar churn, or automated alerts dominate the first pass. 4. Use `batch_read_email` only when snippets are not enough to classify urgency or reply-needed status. 5. Escalate to `read_email_thread` when 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_thread` exposes `total_messages`, which helps detect that. 6. Return the result in explicit Inbox Zero-style buckets such as `Urgent`, `Needs reply soon`, `Waiting`, and `FYI`. ## 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.
Related Skills
teams-notification-triage
Triage recent Microsoft Teams activity into a priority queue or task list for the user.
slack-notification-triage
Triage recent Slack activity into a priority queue or task list for the user.
outlook-email-inbox-triage
Triage an Outlook inbox into actionable buckets such as urgent, needs reply soon, waiting, and FYI using connected Outlook 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
Manage Gmail inbox triage, mailbox search, thread summaries, action extraction, reply drafting, and email forwarding through connected Gmail data. Use when the user wants to inspect a mailbox or thread, search email with Gmail query syntax, summarize messages, extract decisions and follow-ups, prepare replies or forwarded messages, or organize messages with explicit confirmation before send, archive, delete, or label actions.
workflow
Vercel Workflow DevKit (WDK) expert guidance. Use when building durable workflows, long-running tasks, API routes or agents that need pause/resume, retries, step-based execution, or crash-safe orchestration with Vercel Workflow.
verification
Full-story verification — infers what the user is building, then verifies the complete flow end-to-end: browser → API → data → response. Triggers on dev server start and 'why isn't this working' signals.
vercel-storage
Vercel storage expert guidance — Blob, Edge Config, and Marketplace storage (Neon Postgres, Upstash Redis). Use when choosing, configuring, or using data storage with Vercel applications.
vercel-services
Vercel Services — deploy multiple services within a single Vercel project. Use for monorepo layouts or when combining a backend (Python, Go) with a frontend (Next.js, Vite) in one deployment.
vercel-sandbox
Vercel Sandbox guidance — ephemeral Firecracker microVMs for running untrusted code safely. Supports AI agents, code generation, and experimentation. Use when executing user-generated or AI-generated code in isolation.
vercel-queues
Vercel Queues guidance (public beta) — durable event streaming with topics, consumer groups, retries, and delayed delivery. $0.60/1M ops. Powers Workflow DevKit. Use when building async processing, fan-out patterns, or event-driven architectures.
vercel-functions
Vercel Functions expert guidance — Serverless Functions, Edge Functions, Fluid Compute, streaming, Cron Jobs, and runtime configuration. Use when configuring, debugging, or optimizing server-side code running on Vercel.
vercel-flags
Vercel Flags guidance — feature flags platform with unified dashboard, Flags Explorer, gradual rollouts, A/B testing, and provider adapters. Use when implementing feature flags, experimentation, or staged rollouts.