Help us improve
Share bugs, ideas, or general feedback.
From outlook-email
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.
npx claudepluginhub robinebers/converted-plugins --plugin outlook-emailHow this skill is triggered — by the user, by Claude, or both
Slash command
/outlook-email:outlook-email-inbox-triageThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill for direct Outlook inbox-triage requests. Build on the core Outlook Email skill at [../outlook-email/SKILL.md](../outlook-email/SKILL.md), especially its read-first and write-safety 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 Outlook inbox-triage requests. Build on the core Outlook Email skill at ../outlook-email/SKILL.md, especially its read-first and write-safety guidance.
list_messages for recent or unread inbox passes where a bounded mailbox slice is enough.search_messages when the triage request includes lexical search terms, sender filters, attachment constraints, or date scoping.fetch_message or fetch_messages_batch only when snippets are not enough to classify urgency or reply-needed state.mark_email_read_state, move_email, or set_message_categories only if the user explicitly asks you to act on the triage results.list_messages or search_messages before reading full bodies.Urgent, Needs reply soon, Waiting, and FYI.Urgent: direct asks with time pressure, blockers, escalation risk, or operational consequences if ignored.Needs reply soon: direct asks without same-day urgency, active threads where the user is likely the next responder, or follow-ups that will go stale soon.Waiting: threads where the user already replied or where the current blocker belongs to someone else.FYI: announcements, newsletters, calendar noise, transactional mail, and items that do not currently require action.