Automate Google Calendar Events

This skill provides lightweight Google Calendar integration with standalone OAuth authentication - no MCP server required. Authentication runs through scripts/auth.py, and all calendar operations run through scripts/gcal.py, which auto-authenticates on first use if you're not already logged in.

First-time setup opens a browser to authenticate:

python scripts/auth.py login

It can list all calendars, list events (defaulting to the next 30 days on the primary calendar, filterable by time range, specific calendar, or result limit), and fetch full details for a specific event by ID. It creates events with a title, start, and end time, plus optional description, location, attendee list, and target calendar. It updates existing events field by field - title, time, description, location, or attendee list - and deletes events by ID. A find-free-time command locates the first available slot of a given duration across one or more attendees' calendars within a specified time window, useful for scheduling meetings without manual back-and-forth. It also responds to event invitations as accepted, declined, or tentative, with an option to respond without notifying the organizer.

All times use ISO 8601 format with timezone, either UTC (2024-01-15T10:30:00Z) or with an explicit offset (2024-01-15T10:30:00-05:00 for EST). The primary calendar can be referenced with primary or by omitting the calendar flag entirely; other calendars are referenced by the calendar ID returned from the list-calendars command, usually an email address. Auth tokens are stored securely in the system keyring - Keychain on macOS, Windows Credential Locker on Windows, and Secret Service API (GNOME Keyring, KDE Wallet, etc.) on Linux - under the service name google-calendar-skill-oauth, refreshing automatically when expired.

Use it when you need to list, create, inspect, or update Google Calendar events from local scripts, need OAuth-backed calendar automation without standing up an MCP server, or need quick operational access to calendars, schedules, attendees, or event details in a Workspace environment. It requires a Google Workspace account; personal Gmail accounts are not supported.

Use this skill only when the task clearly matches the scope described above - it is not a substitute for environment-specific validation, testing, or expert review, and you should stop and ask for clarification if required inputs, permissions, or success criteria are missing.

Inputs are calendar and event identifiers, time ranges in ISO 8601 format, and event details (title, description, location, attendees). Outputs are calendar and event listings, created/updated event confirmations, or a located free-time slot.

Automation builders on Google Workspace who need scripted, local scheduling operations - listing, creating, updating, or responding to calendar events, or finding meeting availability - without deploying an MCP server.