calendar-scheduling_skill

Overview

This skill provides calendar scheduling capabilities for AI agents, handling natural-language time resolution, multi-provider availability merging, recurrence expansion, and atomic booking with Two-Phase Commit safety. It unifies Google, Outlook, and CalDAV calendars, detects conflicts, and ensures timezone-accurate operations. Use it to automate meeting setup, availability checks, and reliable event creation across calendars.

How this skill works

Start every session by fetching temporal context (current time, timezone, DST) then resolve user datetime expressions into RFC 3339 timestamps. Query calendars or merged availability to find free slots and expand recurrence rules when needed. Before any write, perform an availability check and then call the atomic book_slot tool, which uses lock→verify→write→release to prevent conflicts.

When to use it

• Scheduling a meeting from a natural-language request (e.g., "next Tuesday at 2pm").
• Checking cross-calendar free/busy across Google, Outlook, and CalDAV accounts.
• Expanding RRULEs into concrete event instances for recurring events.
• Converting datetimes between IANA timezones with DST awareness.
• Booking an event atomically while avoiding double-booking in multi-agent environments.

Best practices

• Always call get_temporal_context first to avoid timezone/clock assumptions.
• Resolve all human datetime expressions with resolve_datetime before passing to calendar tools.
• Run check_availability before book_slot; never skip the conflict check.
• Use provider-prefixed calendar IDs (e.g., "google/primary") for multi-calendar operations.
• Use list_events with format: "toon" to reduce token usage when listing ranges.

Example use cases

• User asks "Find a 30-minute slot tomorrow morning" → resolve_datetime → get_availability → present options.
• Book a team standup: resolve start/end times → check_availability on team calendars → book_slot if free.
• Show all instances of a monthly recurring event by calling expand_rrule with dtstart and timezone.
• Convert a scheduled meeting time to a participant’s timezone using convert_timezone.
• Handle booking contention by retrying after lock acquisition failure and suggesting alternatives via find_free_slots.