Agent skill · operations · sickn33
google-calendar-automation
Plan and perform authorized Google Calendar workflows through an existing authenticated integration; inspect events, draft changes and verify results.
Why this skill is useful
Adds executable scripts for Google Calendar automation that provide capabilities not available in standard documentation.
What it needs
Requires python installed locally. Requires google-workspace account access. About 2k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Google Calendar Automation When to Use Inspect calendars, schedules and event details through an already configured integration. Draft or perform explicitly authorized event creation, edits, cancellations or invitation responses. Find possible free slots using only availability the authenticated account may access. Prerequisites and limitations This skill ships instructions only: no OAuth helper, Python client, server or token store is bundled. Discover the available authenticated connector or project-owned Calendar client and inspect its actual tool schema. Do not assume a particular account type, command, authentication flow, notification flag or automatic token refresh. If no integration is configured, provide a draft and explain the missing setup; do not invent commands or fetch a moving external script. Authenticate through the integration's existing consent flow when separately authorized. Never request or echo passwords, cookies, OAuth secrets or token values in chat. Use the least permissions required. Do not inspect calendars outside the task's scope or copy attendee details into unrelated services. Workflow 1. Confirm the account, calendar ID, requested date window, IANA timezone and operation. Resolve ambiguous relative dates and daylight-saving changes before any write. 2. Read the relevant calendars or events with bounded results. Preserve event IDs, recurrence instance IDs and timezone information; distinguish all-day events from timed events. 3. Prepare the proposed title, start/end, description, location, attendees and notification behavior. Use only fields supported by the actual integration. 4. For writes, confirm authorization for the specific change and its notification effects. A request to inspect availability does not authorize creating an event or notifying attendees. Show deletion and recurrence scope before executing a cancellation. 5. Execute the approved operation once. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/google-calendar-automation--7cf3f0