# Calendar

> Google Calendar

- Skill: `mozilla-ai/calendar` (Agent Skill, multi-file: 5 files)
- Install (CLI): `npx skillmds@latest add mozilla-ai/calendar`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mozilla-ai/calendar/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: mozilla-ai (https://skillmd.com/u/mozilla-ai)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/mozilla-ai/calendar

---

# Google Calendar

Google Calendar stores calendars, events, and availability. This integration reads schedules and manages events on calendars the user enabled.

## Available Tools

| Tool | Purpose | Approval |
|------|---------|----------|
| `calendar_list_calendars` | List enabled calendars with access roles and per-tool permissions | Auto |
| `calendar_list_events` | List events in a date range | Auto |
| `calendar_create_event` | Create a new event | Asks user |
| `calendar_update_event` | Update an existing event | Asks user |
| `calendar_delete_event` | Delete an event | Asks user |
| `calendar_check_availability` | Check free/busy status | Auto |

## Date Format

All dates use ISO 8601 format: `2026-03-25T09:00:00`

Use the user's timezone from their profile when constructing dates. Include the timezone
offset in all date strings you pass to calendar tools (e.g. `2026-03-25T09:00:00-04:00`
for Eastern Daylight Time). If the user's timezone is unknown, ask before making any
calendar calls.

## Event Naming Convention

For job-related events, use this format:
- Title: `Job: {Client Name} - {Brief Description}`
- Location: the job site address
- Description: scope of work, materials needed, or other notes

Example: `Job: Test Customer - Kitchen Remodel` at `123 Main Street`

## Finding an event

An event you have not listed this session is unknown, not absent. Never tell
the user an event does not exist, and never create a duplicate event, until
`calendar_list_events` has returned no match for the time range or search
criteria they gave. An event ID you already resolved this session can be
reused without re-listing.

## Availability Checking

Always check availability before suggesting times or creating events:
1. Use `calendar_check_availability` with the proposed date range
2. If busy slots exist, suggest alternative times
3. Only create the event after confirming with the user

## Deduplication

Before creating an event, check for existing events in the same time range:
1. Use `calendar_list_events` for the target date range
2. Look for events with similar titles or times
3. If a match exists, ask the user: "There's already an event at that time. Update it instead?"

## Multi-calendar setups

When `calendar_list_calendars` returns more than one row, check the target calendar's `access_role` before mutating. Read-only roles (`reader`, `freeBusyReader`) reject create, update, and delete. Pass `calendar_id` explicitly on `calendar_create_event`, `calendar_update_event`, and `calendar_delete_event` rather than letting the tool default.

## Common Workflows

### Schedule a new job
1. `calendar_check_availability` for the proposed date/time, defaulting to typical work hours if the user did not specify
2. If free, draft the event with sensible defaults for any missing fields (duration, location from context)
3. `calendar_create_event` with job title format, location, and description
4. Confirm what you assumed: "Scheduled Job: Test Customer - Kitchen Remodel for March 25, 9 AM to 5 PM at 123 Main Street. Change anything?"

### Check the week's schedule
1. `calendar_list_events` for the current week (Monday to Sunday)
2. Summarize events grouped by day
3. Note any free blocks for potential scheduling

### Reschedule a job
1. `calendar_list_events` to find the event and get its ID
2. `calendar_check_availability` for the new proposed time
3. `calendar_update_event` with the event ID and new start/end
4. Confirm the change with the user

### Cancel a job
1. `calendar_list_events` to find the event and get its ID
2. Confirm with the user before deleting
3. `calendar_delete_event` with the event ID

### Find free time for a new job
1. `calendar_check_availability` for the next few days
2. Identify free blocks long enough for the job
3. Suggest available slots to the user

## Tips

- Events created via these tools appear immediately in Google Calendar on all devices
- The event ID returned by `calendar_create_event` can be used later for updates or deletes
- For multi-day jobs, create separate events for each day rather than one spanning event
- When the user mentions a time without a date, assume the next occurrence of that time