Help us improve
Share bugs, ideas, or general feedback.
From gmail
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.
npx claudepluginhub robinebers/converted-plugins --plugin gmailHow this skill is triggered — by the user, by Claude, or both
Slash command
/gmail:gmail-inbox-triageThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
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.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Creates, reads, edits, and analyzes .docx files using docx-js for new documents, pandoc for text extraction, Python scripts for XML unpacking/validation/changes, and LibreOffice for conversions.
Share bugs, ideas, or general feedback.
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.
INBOX and a clear timeframe unless the user asks for a broader audit.search_emails to build a shortlist before reading bodies.batch_read_email only when snippets are not enough to classify urgency or reply-needed status.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.Urgent, Needs reply soon, Waiting, and FYI.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.