google-calendar-automation · sickn33 — Claude Code skill: how it works
google-calendar-automation is a Claude Code skill for managing Google Calendar through an existing authenticated connector. It requires confirmation before scheduling or canceling meetings.
Apache-2.0 ★ 50,109 updated 2026-10-29
npx skills add sickn33/agentic-awesome-skills --skill google-calendar-automation -a claude-codeWhat google-calendar-automation does
This skill bundles guidance rather than runtime code: it includes no OAuth helper, Python library, or token database. The agent relies entirely on an existing authenticated integration available in the workspace. Without a working connector, the model produces a draft and explains what configuration is missing.
The workflow enforces strict checks before mutating data. The assistant confirms the calendar ID, IANA timezone, and date boundaries, accounting for daylight-saving shifts. It preserves recurring event instance identifiers and reads calendar state after network timeouts to prevent duplicate entries.
Security rules prohibit exposing OAuth secrets, cookies, or tokens in conversation history. Checking calendar availability remains separate from scheduling: looking up free slots does not grant permission to create events or notify attendees.
What it helps with
- find available time slots across permitted calendars
- draft calendar invitations with specific IANA timezones
- inspect existing meeting details without modifying them
- prevent duplicate calendar entries during connection timeouts
Example prompts for the agent
- Check my work calendar for a 30-minute slot next Tuesday afternoon in Europe/Rome
- Draft an event titled Sprint Planning for Friday at 10:00 AM, but do not send invites yet
- Inspect event
evt_123and report current attendee responses
How to install google-calendar-automation
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill google-calendar-automation -a claude-code2Manually: put the files in place
~/.claude/skills/google-calendar-automation/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/google-calendar-automation/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill google-calendar-automation -a codex2Manually: put the files in place
.agents/skills/google-calendar-automation/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill google-calendar-automation -a cursor2Manually: put the files in place
.cursor/skills/google-calendar-automation/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install sickn33/agentic-awesome-skills skills/google-calendar-automation2Manually: put the files in place
.github/skills/google-calendar-automation/SKILL.md1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill google-calendar-automation -a gemini-cli2Platform CLI
gemini skills install https://github.com/sickn33/agentic-awesome-skills --path skills/google-calendar-automationManually: put the files in place
.devin/skills/google-calendar-automation/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill google-calendar-automation -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about google-calendar-automation
How to install google-calendar-automation in Claude Code?
Run npx skills add sickn33/agentic-awesome-skills --skill google-calendar-automation -a claude-code. The definition will be placed in ~/.claude/skills/google-calendar-automation/SKILL.md.
What does google-calendar-automation do?
It guides coding assistants through reading schedules, resolving relative dates, preparing drafts, and requiring explicit approvals before modifying Google Calendar data.
Does this skill include an OAuth client or Google Calendar API token?
No, it contains only instructions. You must have an already authenticated integration or client tool configured in your environment.
Source text
SKILL.md · Apache-2.0
--- name: google-calendar-automation description: "Plan and perform authorized Google Calendar workflows through an existing authenticated integration; inspect events, draft changes and verify results." license: Apache-2.0 risk: critical source: community date_added: "2026-02-05" metadata: author: sanjay3290 version: "1.0" --- # 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. On a timeout, read the event state before retrying so a duplicate is not created. Do not automatically broaden calendar access or fall back to a different account. 6. Read back the resulting event when permitted. Report observed state, event ID, timezone and whether notifications were requested. If the provider cannot establish notification delivery or final state, state that uncertainty. ## Example User: "Check my work calendar for a 30-minute slot next Tuesday afternoon in Europe/Rome." Assistant: Resolve Tuesday's date, inspect the explicitly selected calendar's permitted availability, and return candidate slots. Prepare an event draft only if requested. Creating the event, adding attendees or sending invitations requires authorization for that action. ## Limitations - Availability, scopes, account policy and API capabilities depend on the configured integration. - Missing availability is unknown, not proof that an attendee is free. - No bundled runtime or real provider execution is implied by installing this skill. - Do not create, update, cancel or respond to an event without authorization matching that operation.
© sanjay3290 · Apache-2.0 · sickn33/agentic-awesome-skills
Similar skills
All skills for Notes, tasks and projects →google-calendar-automation by other authors comes first.