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.
Best use case
outlook-calendar-group-scheduler is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using outlook-calendar-group-scheduler 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-calendar-group-scheduler/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How outlook-calendar-group-scheduler Compares
| Feature / Agent | outlook-calendar-group-scheduler | 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?
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.
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 Calendar Group Scheduler Use this skill when the scheduling problem is the task. ## Relevant Actions - Use `get_schedule` for attendee and room/resource free-busy windows once you know the concrete schedule identifiers. - Use `find_available_slots` when the problem is mostly about the user's own calendar and buffered openings. - Use `search_events` or `list_events` when you need conflict context before ranking options. - Use `create_event` only after the winning slot and attendee set are settled. ## Outlook Product Framing - Treat free/busy visibility, work hours, and work location as first-class scheduling evidence when full event detail is unavailable. - Treat attendee response state and organizer logistics as part of scheduling, not just the final event body. - When rooms or resources are visible, treat them as Outlook-style scheduling constraints rather than a separate "room finder" workflow. ## Workflow 1. Ground the scheduling problem first: date window, duration, timezone, required attendees, optional attendees, and any hard constraints such as "this week", "afternoons only", or "avoid lunch". 2. If the scheduling window is ambiguous, assess the meeting stakes before choosing a default search window. For relatively high-stakes meetings, go back to the user and suggest tightening the timeline, for example to the next week. For lower-stakes or more casual group scheduling, default to a near-term search such as the next 1 to 3 weeks. 3. Normalize the request into explicit candidate windows before ranking anything. 4. Rank slots, do not enumerate everything. Optimize for a short list of strong options. 5. Treat `Busy` and `Out of Office` as harder constraints than `Tentative` or `Working Elsewhere` unless the user says otherwise. 6. Prefer slots that minimize conflict cost, fit within work hours, and avoid avoidable hybrid-work friction such as forcing an in-office room meeting onto remote-heavy attendees. 7. When rooms, resources, or building context are available, prefer slots that keep the meeting logistically coherent instead of treating time as the only variable. 8. If shared-calendar visibility is partial, say when a recommendation is based on free/busy signals rather than full event detail. ## Ranking Heuristics - Favor required-attendee fit over optional-attendee fit. - Favor slots that avoid very early or very late local times for distributed attendees. - Favor slots that stay inside work hours and avoid consuming the only large free block in someone's day unless the meeting is clearly important. - Favor a small number of high-confidence options over a long weak list. - When two slots are similar, prefer the one that causes less calendar fragmentation. - When one attendee is only `Tentative` or `Working Elsewhere`, describe that as a softer constraint instead of silently treating it as unavailable. - When one option aligns better with attendees' work locations or room logistics, explain that advantage explicitly. ## Output Conventions - Return 2-4 candidate slots by default. - For each slot, say why it works and who, if anyone, would be inconvenienced. - If there is no clean option, say what tradeoff the best slot is making.
Related Skills
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-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-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.
google-calendar
Manage scheduling and conflicts in connected Google Calendar data. Use when the user wants to inspect calendars, compare availability, review conflicts, find a meeting room, review event notes or attachments, or draft exact create, update, reschedule, or cancel changes with timezone-aware details.
google-calendar-meeting-prep
Build a practical meeting prep brief from a connected Google Calendar event and its nearby 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.
google-calendar-group-scheduler
Find and rank good meeting times for multiple people using connected Google Calendar data. Use when the user wants to schedule a group meeting, compare candidate slots across several attendees, find the best compromise time, or add a room check after narrowing the attendee-compatible options.