Gmail Inbox Triage Skill for Codex

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.

9k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

4915

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/openai/plugins --skill gmail-inbox-triage

What comes with it

35 615 bytes besides the instruction

agents/openai.yaml

assets/gmail-small.svg

assets/gmail.png

The instruction itself

5 sections, as written by the author

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 INBOX and a clear timeframe unless the user asks for a broader audit.
Use search_emails to build a shortlist before reading bodies.
Exclude obvious noise early if newsletters, calendar churn, or automated alerts dominate the first pass.
Use batch_read_email only when snippets are not enough to classify urgency or reply-needed status.
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.
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.

Other skills for the same job

different authors, same section of the catalogue

Meeting Insights Analyzer

by frostant

×8

Analyzes meeting transcripts and recordings to uncover behavioral patterns, communication insights, and actionable feedback. Identifies when you avoid conflict, use filler words, dominate conversations, or miss opportunities to listen. Perfect for professionals seeking to improve their communication and leadership skills.

Toolkit for creating animated GIFs optimized for Slack, with validators for size constraints and composable animation primitives. This skill applies when users request animated GIFs or emoji animations for Slack from descriptions like "make me a GIF for Slack of X doing Y".

53k tokens scripts

Developer Growth Analysis

by frostant

×6

Analyzes your recent Claude Code chat history to identify coding patterns, development gaps, and areas for improvement, curates relevant learning resources from HackerNews, and automatically sends a personalized growth report to your Slack DMs.

Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack.

A skill that creates new Claude skills and automatically shares them on Slack using Rube for seamless team collaboration and skill discovery.

Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.

Interactive daily standup/meeting update generator. Use when user says 'daily', 'standup', 'scrum update', 'status update', 'what did I do yesterday', 'prepare for meeting', 'morning update', or 'team sync'. Pulls activity from GitHub, Jira, and Claude Code session history. Conducts 4-question interview (yesterday, today, blockers, discussion topics) and generates formatted Markdown update.

8k tokens scripts

Professional Communication

by softaworks

×2

Guide technical communication for software developers. Covers email structure, team messaging etiquette, meeting agendas, and adapting messages for technical vs non-technical audiences. Use when drafting professional messages, preparing meeting communications, or improving written communication.

12k tokens

How to use it

Copy the folder

Take openai/gmail-inbox-triage from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.