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.
Best use case
outlook-email-inbox-triage is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using outlook-email-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/outlook-email-inbox-triage/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How outlook-email-inbox-triage Compares
| Feature / Agent | outlook-email-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 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.
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.
Related Guides
SKILL.md Source
# Outlook Email Inbox Triage ## Overview 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. ## Relevant Actions - Use `list_messages` for recent or unread inbox passes where a bounded mailbox slice is enough. - Use `search_messages` when the triage request includes lexical search terms, sender filters, attachment constraints, or date scoping. - Use `fetch_message` or `fetch_messages_batch` only when snippets are not enough to classify urgency or reply-needed state. - Use `mark_email_read_state`, `move_email`, or `set_message_categories` only if the user explicitly asks you to act on the triage results. ## Workflow 1. Default to the inbox and a clear timeframe unless the user asks for a broader audit. 2. Build a shortlist with `list_messages` or `search_messages` before reading full bodies. 3. Exclude obvious noise early if newsletters, calendar churn, or automated alerts dominate the first pass. 4. Expand only the messages whose urgency, ownership, or reply-needed status is unclear from the first pass. 5. Return explicit buckets such as `Urgent`, `Needs reply soon`, `Waiting`, and `FYI`. 6. If the user asks to clean up the mailbox after triage, keep the classification and the mailbox actions clearly separated. ## Bucket Heuristics - `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. ## 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
Email sending integration guidance — Resend (native Vercel Marketplace) with React Email templates. Covers API setup, transactional emails, domain verification, and template patterns. Use when sending emails from a Vercel-deployed application.
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
Triage Outlook mail, extract tasks, clean up subscriptions, and draft responses. Use when the user asks to inspect an Outlook inbox or thread, summarize open actions and deadlines, clean up newsletters, draft replies or forwards, or organize mailbox follow-up work before any send or cleanup action.
outlook-email-task-extraction
Extract action items, deadlines, commitments, and owners from Outlook email threads and mailbox searches. Use when the user wants a task list from one thread, several related messages, or a mailbox slice, including who owes what and when.
outlook-email-subscription-cleanup
Clean up Outlook newsletters and recurring subscription email safely. Use when the user wants to unsubscribe, separate newsletters from human mail, move recurring senders into folders, or organize low-signal subscription traffic without losing important messages.
outlook-email-reply-drafting
Draft Outlook email replies safely from connected mailbox context. Use when the user wants to reply to a thread, decide whether to reply-all, prepare a draft before sending, or turn the latest Outlook message into a polished response.
outlook-calendar
Handle Outlook Calendar workflows. Use when the user asks for schedule understanding, availability checks, meeting scheduling, intelligent rescheduling, meeting prep, reminder updates, RSVP responses, recurring maintenance, travel coordination, deadline planning, or safe create, update, reschedule, or cancel changes with timezone-aware event times and attendee validation.
outlook-calendar-meeting-prep
Build a practical meeting prep brief from an Outlook Calendar event and its nearby Microsoft context. Use when the user wants to prepare for an upcoming meeting, understand what to read beforehand, pull in linked notes or docs, or get a concise brief on what the meeting appears to require.
outlook-calendar-group-scheduler
Find and rank good meeting times for several people using Outlook Calendar data. Use when the user wants to schedule a meeting, compare candidate slots across attendees, find the best compromise time, or add a room/resource check after narrowing the attendee-compatible options.
outlook-calendar-free-up-time
Find ways to open up meaningful free time in Outlook Calendar. Use when the user wants to clear part of their schedule, make room for focus time, create a longer uninterrupted block, or see the smallest set of calendar changes that would give time back.
outlook-calendar-daily-brief
Build polished one-day Outlook Calendar briefs. Use when the user asks for today, tomorrow, or a specific date summary with an agenda, conflict flags, free windows, remaining-meeting readouts, or a calendar brief, and Outlook Calendar is available.