Google Calendar

A straightforward wrapper around Google's Calendar and Tasks APIs that handles OAuth for you and gives Claude shell access to your schedule. You get commands for the usual suspects: list, create, update, delete events and tasks, plus free/busy lookups and search. Setup requires a Google Cloud OAuth client and a quick auth flow, then everything lives in config files at ~/.config/google-calendar. The tool supports multiple accounts via different token files and lets you hit arbitrary API endpoints with the call command when the convenience methods aren't enough. Useful if you want Claude to actually read your calendar or manage tasks without building the OAuth dance yourself.

skills.sh installs: 451
GitHub stars: 3
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add dotneet/claude-code-marketplace --skill google-calendar --agent claude-code

Installs into .claude/skills of the current project.

Files

Google Calendar + Tasks Access

Quick start

Create a Google Cloud OAuth client (Desktop app) and save the credentials JSON to ~/.config/google-calendar/credentials.json.

Install dependencies (venv recommended):

python3 -m venv ~/.config/google-calendar/venv
~/.config/google-calendar/venv/bin/pip install -r <skill_dir>/scripts/requirements.txt

Authenticate and store a token:
- Calendar only:
  - <skill_dir>/scripts/gcal-auth
- Tasks only:
  - <skill_dir>/scripts/gcal-auth --scopes https://www.googleapis.com/auth/tasks
- Calendar + Tasks (single token):
  - <skill_dir>/scripts/gcal-auth --scopes https://www.googleapis.com/auth/calendar https://www.googleapis.com/auth/tasks
Call the API:
- <skill_dir>/scripts/gcal list-calendars

Credentials and tokens

Credentials are expected at ~/.config/google-calendar/credentials.json by default.
Tokens are stored at ~/.config/google-calendar/token.json by default.
Use --token or GCAL_TOKEN_PATH to switch accounts or isolate environments.