google-calendar

name	Google Calendar
catalog_line	Use Google Calendar safely from an agent: read, create, reschedule, cancel, and sync without duplicates.
description	Use Google Calendar safely from an AI agent. Use when reading, creating, rescheduling, cancelling, or syncing calendar events; choosing calendar scope; preventing duplicate events; handling recurring events; or linking calendar time to projects and tasks.
skill_type	procedure
altitude	domain
activation	progressive
preserve_markdown	true
legacy_paths	["google-calendar","google-workspace/google-calendar","google-calendar-for-ai-agents-search-before-you-create","google_calendar_for_ai_agents_search_before_you_create","apps/web/src/content/blogs/agent-skills/google-calendar-for-ai-agents-search-before-you-create.md"]
reference_modules	[{"id":"google_calendar.public_safe_write_rules","name":"Public Safe Calendar Write Rules","summary":"Portable checklist for scope, lookup, create/update/delete, recurrence, time zones, and sync boundaries.","when_to_load":["When using the portable bundle outside BuildOS.","Before creating, updating, deleting, or rescheduling calendar events.","When recurrence, attendee notification, duplicate event, or sync risk is present."],"path":"references/public-safe-write-rules.md","visibility":"public"}]
path	apps/web/src/lib/services/agentic-chat/tools/skills/definitions/google_calendar/SKILL.md

Google Calendar

Identity

Google Calendar is live operational state. Calendar writes should be conservative because bad writes change someone's day.

This is a procedure skill at domain altitude: an operational runbook for using Google Calendar safely from an AI agent. The spine is an ordered write workflow (choose scope → bounded lookup → decide create-vs-update → mutate by exact ID → report), carried by a large secondary body of normative decision rules and guardrails.

Activation

• Read calendar events in a time window.
• Create work blocks, meetings, reminders, or follow-up sessions.
• Reschedule or cancel events.
• Search for an existing meeting or work block.
• Find availability.
• Handle recurring events or one-off exceptions.
• Diagnose duplicate event or sync risk.
• Link calendar time to a task, project, CRM record, or workflow.

Judgment

The core rule is simple: search before create.

Create only after choosing scope, inspecting the relevant time window, and deciding the request is not really an update to an existing event.

Read Rules

• Use explicit start and end bounds.
• Carry timezone when available.
• Use text search for lookup tasks like "find the design review."
• Use free/busy or availability tools when the user asks for an open slot.
• Return concrete recurring instances when the user asks what is on the calendar.

Create Rules

• Never create blindly.
• Search the target time window first.
• Prefer adding metadata that links the event to the originating task, project, CRM record, or workflow.
• If confidence is low, ask before creating.
• Do not create a replacement event as a hidden fallback for a failed update.

Update and Delete Rules

• Use exact event IDs or local mapped IDs.
• Verify calendar scope before mutation.
• Verify whether attendees may be notified.
• For important or complex writes, read the existing event first and merge intended changes.
• Do not mutate based on vague title matching alone.

Recurrence Rules

• "Only this one" means edit the specific instance.
• "From now on" means edit future instances or the future series shape.
• "All of them" means edit the full series.
• If wording is ambiguous, ask.
• Never silently apply a broad recurrence edit.

Time Rules