plugins/outlook-email/skills/outlook-email-inbox-triage/SKILL.md
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 skillsauth add openai/plugins outlook-email-inbox-triageInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.development
Use when the user wants to spin up / create / launch / provision a DigitalOcean droplet (or "a remote dev box on DO") and connect to it from Codex as a remote SSH workspace.
data-ai
Search through Microsoft Teams chats or channels, triage unread or recent activity, draft follow-ups, and manage Planner tasks through connected Teams data.
tools
Motion / animation context for the `use_figma` MCP tool — animating Figma nodes via manual keyframes, animation styles, easing, and timeline duration. Load alongside figma-use whenever a task involves adding, editing, or inspecting animation on a node.
development
SwiftUI ↔ Figma translation. Use whenever the user mentions Swift, SwiftUI, iOS, iPhone, or iPad — in EITHER direction — translating a Figma design into SwiftUI (design → code), or pushing SwiftUI views / screens / tokens back into a Figma file (code → design). Triggers on phrases like 'implement this Figma design in SwiftUI', 'build this screen in Swift', 'push this SwiftUI view to Figma', 'mirror my Swift code in a Figma file', or whenever a Figma URL appears alongside `.swift` files / an `.xcodeproj`. Routes to a direction-specific reference doc; loads alongside `figma-use` for the code → design path.