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.
Best use case
outlook-calendar-free-up-time is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using outlook-calendar-free-up-time 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-free-up-time/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How outlook-calendar-free-up-time Compares
| Feature / Agent | outlook-calendar-free-up-time | 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 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.
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.
SKILL.md Source
# Outlook Calendar Free Up Time Use this skill when the goal is to create time, not just inspect time. ## Relevant Actions - Use `list_events` to map the current fragmentation and identify movable candidates. - Use `fetch_event` when one candidate needs a closer read before proposing a change. - Use `find_available_slots` to verify whether a better block exists on the user's own calendar. - Use `get_schedule` before moving attendee-heavy meetings when cross-attendee availability matters. - Use `update_event` only after the proposal is grounded and the intended event is unambiguous. ## Workflow 1. Start by identifying the target: today, tomorrow, this afternoon, a specific day, or a broader window. 2. Optimize for contiguous free blocks, not raw free-minute totals. 3. Identify which meetings are likely fixed and which are more movable before proposing changes. 4. Look for the smallest edit set that creates a meaningful uninterrupted block. 5. Prefer solutions that reduce fragmentation across the rest of the day, not just one local gap. 6. Treat `Tentative`, `Free`, self-created placeholders, and lightly attended internal holds as lower-cost candidates than hard external meetings, accepted commitments, or `Out of Office` blocks. 7. When work hours or work location are relevant, prefer openings that produce a useful block inside the user's actual workday. 8. If no clean block exists, show the best partial win and what tradeoff it requires. ## Prioritization Heuristics - Protect hard anchors such as external meetings, major reviews, commute buffers, and stable lunch windows. - Move lower-cost meetings first, such as tentative holds, lightweight internal syncs, or self-created placeholders. - When two meetings are similarly movable, prefer moving a 1:1 over a larger group meeting because it creates less attendee thrash. - Favor one or two coherent shifts over a chain of many tiny moves. - Prefer creating one useful block over scattering a few small openings. - Preserve existing Teams links and attendee lists unless the user wants to change them. - If a meeting has weak attendee commitment, interpret that in context rather than as a blanket signal. Far-future weak commitment is normal; imminent weak commitment is a much stronger sign that the meeting may be movable or unstable. ## Output Conventions - Show the before-and-after effect of the proposal. - Name the block created and the minimum meetings that would need to move. - If suggesting multiple options, keep them short and explain the tradeoff for each.
Related Skills
runtime-cache
Vercel Runtime Cache API guidance — ephemeral per-region key-value cache with tag-based invalidation. Shared across Functions, Routing Middleware, and Builds. Use when implementing caching strategies beyond framework-level caching.
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-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-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.