Read Google Calendar schedules, check availability, and create or update events as requested. Handle time zones, all-day events, and recurring appointments while confirming event details and making invitation notifications clear.
Read schedules, check availability, and create or update Google Calendar events when the user asks to work with their calendar.
Review the instructions the agent will receive before you install.
Prefer an already connected Calendar tool. Installing this skill does not connect an account. Direct API access needs Calendar API enabled and the user's own OAuth client. For a user-authorized read-only setup:
gcloud auth application-default login --client-id-file=/path/to/client.json --scopes=https://www.googleapis.com/auth/calendar.events.readonly
This replaces existing Application Default Credentials; explain that effect
before changing auth. Request only scopes needed for the task, not Gmail access.
Use calendar.events for authorized event edits or a free/busy scope when only
availability is needed. Keep tokens in the credential flow, never in chat.
GET https://www.googleapis.com/calendar/v3/calendars/primary/events
with RFC3339 timeMin/timeMax, singleEvents=true, orderBy=startTime;
URL-encode values and follow nextPageToken as needed.Do not invite people, move events, or delete a series on your own initiative.
References: Google OAuth setup, Calendar scopes.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Split a large goal into clearly bounded tasks that can run in parallel. Coordinate existing agent and worktree tools, then combine and verify the results. The skill starts only when explicitly requested.
Generate independent options for design, implementation, explanations, or debugging, then compare them using one shared rubric. Code candidates use separate working copies and undergo independent verification before a winner is presented for review.
Check Codewhale release readiness through ordered tests, builds, version checks, and manual terminal checks. Record command results and observed behavior, including responsiveness, route isolation, and follow-up input handling, while explicitly identifying any skipped checks.
Operate desktop apps and isolated browsers on registered computers by inspecting interface controls, entering information, and checking results. The skill also covers screenshots and recording, with separate routing for the user's signed-in Chrome through Chromewhale.
Check a local Codewhale checkout before contributing: inspect branch and sync status, build the CLI, and run the repository’s CI checks. Present recent commits and changelog entries from local files, with clear status for each step.
Builds and installs Codewhale with a source revision identifier, then verifies the installed version in a fresh shell. It guides hands-on runtime checks for interface behavior, routing, approvals, and other changes that automated tests may miss.