google-calendar
Manage scheduling and conflicts in connected Google Calendar data. Use when the user wants to inspect calendars, compare availability, review conflicts, find a meeting room, review event notes or attachments, or draft exact create, update, reschedule, or cancel changes with timezone-aware details.
Best use case
google-calendar is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Manage scheduling and conflicts in connected Google Calendar data. Use when the user wants to inspect calendars, compare availability, review conflicts, find a meeting room, review event notes or attachments, or draft exact create, update, reschedule, or cancel changes with timezone-aware details.
Teams using google-calendar should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/google-calendar/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How google-calendar Compares
| Feature / Agent | google-calendar | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Manage scheduling and conflicts in connected Google Calendar data. Use when the user wants to inspect calendars, compare availability, review conflicts, find a meeting room, review event notes or attachments, or draft exact create, update, reschedule, or cancel changes with timezone-aware details.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Google Calendar ## Overview Use this skill to turn raw calendar data into clear scheduling decisions. Keep answers grounded in exact dates, times, and calendar evidence. ## Preferred Deliverables - Availability summaries with exact candidate slots, timezone, and conflicts. - Room or resource recommendations grounded in actual calendar availability or prior meeting patterns. - Event change proposals that show the current event and the intended update. - Final event details that are ready to create or confirm. ## Workflow 1. Read the relevant calendar state first so the request is grounded in actual events, calendars, and time windows. 2. Normalize relative time language into explicit dates, times, and timezone-aware ranges before reasoning about availability. 3. When the user leaves something ambiguous, inspect previous calendar data for a clear precedent before choosing a default. Follow established patterns when they are obvious, such as using the user's usual meeting duration if similar events are consistently 30 minutes. 4. For room-finding requests, do not assume there is a reliable global room search. In this V1 flow, mine a reasonable window of past meetings, locations, and resource attendees to build a candidate room list, then compare availability on that concrete set. 5. When notes, prep context, or missing details matter, inspect the event payload before proposing a change. 6. Surface conflicts, transparent holds, and missing meeting details before suggesting a write. 7. If the request is still ambiguous after checking for precedent, summarize the candidate slots or exact diff before writing anything. ## Write Safety - Preserve source event details unless the user asked to change them. - Treat deletes and broad availability changes as high-impact actions. - If multiple calendars or similarly named events are in play, identify the intended one explicitly before editing. - Treat missing title, attendees, location, meeting link, or timezone as confirmation points rather than assumptions. ## Output Conventions - Present scheduling summaries with exact weekday, date, time, and timezone. - When sharing availability, say why a slot works or conflicts instead of listing raw times without context. - When suggesting a room or resource, name the likely room and why it is a fit, such as prior usage, matching location, or open busy windows. - When comparing options, keep the list short and explain the tradeoff for each slot. - When the user asks for meeting notes or prep context, mention whether the answer came from the event description, an attachment, or both. ## Example Requests - "Check my availability with Priya this Thursday afternoon and suggest the best two meeting slots." - "Find a room for the weekly team sync next Tuesday by checking rooms we've used before and which ones are free." - "Move the design review to next week and keep the same attendees and Zoom link." - "Summarize my calendar for tomorrow and flag anything that overlaps or leaves no travel time." - "Draft the final event details for a 30 minute customer sync at 2 PM Pacific on Friday."
Related Skills
outlook-calendar
Handle Outlook Calendar workflows. Use when the user asks for schedule understanding, availability checks, meeting scheduling, intelligent rescheduling, meeting prep, reminder updates, RSVP responses, recurring maintenance, travel coordination, deadline planning, or safe create, update, reschedule, or cancel changes with timezone-aware event times and attendee validation.
outlook-calendar-meeting-prep
Build a practical meeting prep brief from an Outlook Calendar event and its nearby Microsoft context. Use when the user wants to prepare for an upcoming meeting, understand what to read beforehand, pull in linked notes or docs, or get a concise brief on what the meeting appears to require.
outlook-calendar-group-scheduler
Find and rank good meeting times for several people using Outlook Calendar data. Use when the user wants to schedule a meeting, compare candidate slots across attendees, find the best compromise time, or add a room/resource check after narrowing the attendee-compatible options.
outlook-calendar-free-up-time
Find ways to open up meaningful free time in Outlook Calendar. Use when the user wants to clear part of their schedule, make room for focus time, create a longer uninterrupted block, or see the smallest set of calendar changes that would give time back.
outlook-calendar-daily-brief
Build polished one-day Outlook Calendar briefs. Use when the user asks for today, tomorrow, or a specific date summary with an agenda, conflict flags, free windows, remaining-meeting readouts, or a calendar brief, and Outlook Calendar is available.
google-slides
Inspect, create, import, summarize, and update Google Slides presentations through connected Google Slides data. Use when the user wants to find a deck, read slide structure, summarize a presentation or specific slide, understand charts, graphs, or other slide visuals by combining slide text with thumbnail-based image understanding, create a new presentation, import a `.ppt`, `.pptx`, or `.odp`, or make general content edits in Google Slides. For visual polish on an existing deck, such as formatting cleanup, alignment fixes, overflow cleanup, or slide-by-slide deck cleanup, prefer `google-slides-visual-iteration`.
google-slides-visual-iteration
Iteratively inspect and polish existing connected Google Slides presentations in Codex using slide thumbnails plus raw Slides edits. Use when a user asks to fix a slide visually, clean up formatting, improve slide quality, make a deck look better, fix alignment, spacing, overlap, overflow, crowding, awkward whitespace, or deck-wide visual consistency in an existing Google Slides deck or shared Slides link, especially when the work should follow a thumbnail -> diagnose -> batch_update -> re-thumbnail verification loop.
google-slides-template-surgery
Perform structural rework in connected Google Slides decks. Use when local visual cleanup is not enough and repeated layout defects require batch_update structure edits plus strict verification.
google-slides-template-migration
Migrate a Google Slides deck onto a target template. Use when the user wants to preserve source content while rebuilding slides from a branded template structure instead of making incremental in-place edits.
google-slides-import-presentation
Import a local `.ppt`, `.pptx`, or `.odp` file into Google Slides, verify the resulting native deck, and hand it off to the right follow-on workflow. Use when the user wants to convert a presentation file into a native Google Slides deck before follow-on work.
google-sheets
Analyze and edit connected Google Sheets with range precision. Use when the user wants to find a spreadsheet, inspect tabs or ranges, search rows, plan formulas, clean or restructure tables, write concise summaries, or make explicit cell-range updates.
google-sheets-formula-builder
Design, repair, and roll out Google Sheets formulas with better syntax recall and validation discipline. Use when the user wants to add a formula column, fix a broken formula, choose between a row formula and a spill formula, build a lookup or filter formula, or turn repeated logic into a reusable named function.