Skip to main content
Skill Gallery
Connected Tools Google Workspace Provider

Google Calendar For AI Agents: Search Before You Create

Google Calendar is one of the best first integrations for AI agents, but naive agents create duplicates, mis-handle time zones, and break recurring events. This guide gives you the operating rules and a portable SKILL.md definition you can adapt.

Try in BuildOS Read guide SKILL.md

Sources

8

Refs

1

Steps

8

Outputs

2

What It Does

Use it when the job needs a real procedure.

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.

Outputs

safe action planevent mutation checklist

The page is for humans first. The files in the rail make the same procedure available to agents.

Try It

Start with one of these prompts.

Help me safely create a calendar event without duplicating anything.

Try in BuildOS

Audit this calendar update plan for recurrence, time zone, and exact-ID risk.

Try in BuildOS

Procedure

The operating path

  1. 1

    Choose scope first: primary calendar, shared calendar, project calendar, or explicit calendar ID.

  2. 2

    Use bounded lookup: search with an explicit time window and timezone.

  3. 3

    Search for likely matches by title, time overlap, attendees, linked task/project metadata, local mapping, and external event IDs.

  4. 4

    If a likely event exists, update it, ask, or confirm whether the user wants an additional event.

  5. 5

    Create only when no reasonable match exists or the user explicitly wants another event.

  6. 6

    For update/delete, use exact IDs. Prefer local mapping, then external event ID plus calendar ID.

  7. 7

    Treat recurring events as high risk. Clarify whether the user means one instance, future instances, or the whole series.

  8. 8

    Report what changed and mention attendee notifications or sync implications when relevant.

Boundaries

What the skill refuses or checks carefully

Do not create a calendar event before searching the relevant window.

Do not mutate by vague title matching alone.

Do not silently apply broad recurrence edits.

Do not invent calendar scope.

Do not hide failed updates by creating replacement events.

Do not merge search logic with background sync-token state.

Examples

Runtime examples

Reschedule an existing meeting

  • Choose calendar scope.
  • Search the target day for the meeting title and overlapping attendees.
  • Inspect likely matches.
  • If one obvious match exists, update that event ID.

Create a project work block

  • Resolve the project or task if the agent has access to one.
  • Search the target week for existing related work blocks.
  • If a work block exists, ask whether to move it or add another session.
  • If none exists, find a slot and create the event.

Move one recurring instance

  • Search the narrow target window.
  • Identify the concrete recurring instance.
  • Update only that instance.
  • Preserve the rest of the series.