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.
Best use case
outlook-email-reply-drafting is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using outlook-email-reply-drafting 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-reply-drafting/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How outlook-email-reply-drafting Compares
| Feature / Agent | outlook-email-reply-drafting | 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?
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.
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 Reply Drafting ## Overview Use this skill when the reply itself is the task. Read enough mailbox context to understand the latest ask, then default to a draft unless the user clearly asked you to send. Outlook reply writes are plain-text only. If the user asks for HTML formatting, styled sections, or layout-specific markup, say briefly that Outlook reply actions here only support plain text, then convert the request into a clean plain-text reply instead of planning an HTML body. ## Relevant Actions - Use `search_messages` or `list_messages` to find the right thread when the user names a topic rather than a concrete message. - Use `fetch_message` or `fetch_messages_batch` when the latest snippet is not enough to understand tone, commitments, or the actual ask. - Use `create_reply_draft` for reply and reply-all drafts tied to an existing message. - Use `reply_to_email` only when the user explicitly asked to send and the content is fully grounded. - Use `draft_email` only for net-new messages or when the task is not a direct reply to an existing message. ## Workflow 1. Identify the exact source message or thread before drafting. 2. Read the most recent message first, then enough nearby context to understand participants, status, commitments, and tone. 3. Decide whether reply-all is necessary based on shared context, not just recipient count. 4. Draft the reply in the thread's tone unless the user asks for a deliberate change, but keep the draft plain text. 5. If the draft depends on missing facts, produce the best draft you can and list the unresolved details separately. 6. If the user later approves sending, reuse the thread-grounded draft instead of recreating the reply from scratch. ## Safety - Preserve dates, commitments, names, links, and quoted facts unless the user asks to change them. - Do not invent availability, approvals, ownership, or promises that are not already established in mailbox context. - Treat reply-all as a deliberate choice. If the audience is ambiguous, explain the safest default. - If the user says "send" but the content still depends on unstated choices, stop and ask the narrowest necessary confirmation question. - Do not promise HTML email formatting or markup-specific rendering. Express structure with plain-text paragraphs, lists, and raw links, and tell the user when that means a requested formatting detail cannot be preserved exactly. ## Output - Provide a ready-to-send plain-text draft with greeting, body, and closing when appropriate. - If important assumptions remain, list them immediately after the draft. - If you are recommending a reply-all decision, say why in one short line.
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-reply-drafting
Draft Microsoft Teams replies from available context. Use when the user wants help finding messages that likely need a response and preparing reply drafts.
slack-reply-drafting
Draft Slack replies from available context. Use when the user wants help finding messages that likely need a response and preparing reply drafts.
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-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.
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.