Automate Google Calendar Events

This skill gives lightweight Google Calendar integration with standalone OAuth authentication, requiring no MCP server. It requires a Google Workspace account - personal Gmail accounts are not supported. First-time setup runs python scripts/auth.py login to authenticate via browser, status to check auth state, and logout when needed; all other commands run through scripts/gcal.py, which auto-authenticates on first use. It lists calendars (list-calendars) and events (list-events, with --time-min/--time-max, --calendar, and --max-results flags, defaulting to the primary calendar's next 30 days), retrieves a single event's details (get-event EVENT_ID), creates events with a title, start, and end time plus optional --description, --location, --attendees, and --calendar, updates an event's summary, time, description, location, or attendees (update-event), and deletes events (delete-event). It finds the first available meeting slot for one or more attendees given a time window and duration (find-free-time), and responds to an invitation as accepted, declined, or tentative, with an optional --no-notify flag to skip notifying the organizer (respond-to-event).

Use it to list, create, inspect, or update Google Calendar events from local scripts, for OAuth-backed calendar automation without standing up an MCP server, or for quick operational access to calendars, schedules, attendees, or event details in a Workspace environment. It does not apply to personal Gmail accounts, which are unsupported.

Inputs: event details (title, ISO 8601 start/end times, optional description/location/attendees), a calendar ID (primary or an email address from list-calendars), and OAuth credentials. Outputs: calendar and event listings, created/updated/deleted event confirmations, a proposed free-time slot matching all attendees' availability, and an updated RSVP status on an invitation. All times use ISO 8601 format with timezone, either UTC (2024-01-15T10:30:00Z) or an offset (2024-01-15T10:30:00-05:00 for EST).

Google Calendar via standalone OAuth (no MCP server required), and the system keyring for token storage - macOS Keychain, Windows Credential Locker, or Linux Secret Service API (GNOME Keyring, KDE Wallet) under the service name google-calendar-skill-oauth. Tokens refresh automatically when expired via Google's cloud function.

python scripts/gcal.py find-free-time \
    --attendees me user1@example.com user2@example.com \
    --time-min "2024-01-15T09:00:00Z" \
    --time-max "2024-01-19T17:00:00Z" \
    --duration 60

Users on a Google Workspace account who need quick, script-driven calendar automation - listing, creating, updating, or scheduling around events - without deploying an MCP server. The primary calendar is addressed with primary or by omitting the --calendar flag entirely, while any other calendar is addressed by the calendar ID returned from list-calendars, which is usually an email address such as work@example.com.