Triage Outlook mail, extract tasks, clean up subscriptions, draft responses, and route shared mailbox work. Use when the user asks to inspect an Outlook inbox or thread, summarize open actions and deadlines, clean up newsletters, draft replies or forwards, organize mailbox follow-up work, or act on a delegated/shared Outlook mailbox.
Use this skill to turn Outlook Email inbox and thread context into clear summaries, action lists, and ready-to-review drafts. Prefer Outlook-native list and search flows to build a shortlist, expand only the messages that matter, and treat mailbox mutations as separate explicit actions.
Outbound Outlook email writes are plain-text only. When drafting, replying, scheduling, or sending, do not plan around HTML bodies, rich formatting, tracking pixels, or formatting-dependent layouts. If the user asks for richer formatting, say briefly that Outlook email write actions here only support plain text, then translate the request into the clearest plain-text equivalent.
| Workflow | Skill |
|---|---|
| Inbox triage, urgency ranking, and reply-needed detection | ../outlook-email-inbox-triage/SKILL.md |
| Reply drafting, reply-all decisions, and send-vs-draft handling | ../outlook-email-reply-drafting/SKILL.md |
| Action-item, deadline, and commitment extraction | ../outlook-email-task-extraction/SKILL.md |
| Newsletter and subscription cleanup | ../outlook-email-subscription-cleanup/SKILL.md |
| Delegated or shared mailbox reads, sends, read-state changes, and moves | ../outlook-email-shared-mailboxes/SKILL.md |
list_messages or search_messages to build the first-pass shortlist. These calls already return rich enough fields for most inbox navigation and thread-selection tasks.fetch_message or fetch_messages_batch only when the user explicitly needs fuller body content, longer context, or tighter evidence for task extraction.list_attachments and fetch_attachment when attachment metadata or file contents change the answer.create_reply_draft, create_forward_draft, or draft_email.schedule_email when the user explicitly wants a delayed send or send-later workflow rather than an immediate send.mark_email_read_state, move_email, set_message_categories, create_category, create_mail_folder.get_unsubscribe_info before assuming a safe unsubscribe path. unsubscribe_via_mailto only covers mailto: targets.list_messages, fetch_message, send_email, mark_email_read_state, or move_email for another mailbox.schedule_email.list_messages or mailbox-wide search/list results over fetch_message. Treat fetch_message category readback as unreliable if it returns categories: null after a successful category write.Keep these workflows in the base Outlook Email skill instead of splitting them further for now:
If Outlook mailbox data is missing or incomplete, say that Microsoft Outlook access may be unavailable or scoped to the wrong mailbox or thread, then ask the user to reconnect or clarify the target.
If category writes succeed but direct message fetches return categories: null, say that the Outlook connector appears to have a category readback inconsistency. Verify categories from list_messages or broader mailbox scans instead of single-message fetches, and note the limitation clearly to the user.