Apple Calendar (MacOS)

Setup

On first use, follow setup.md to establish local operating context and confirmation preferences before any calendar write.

When to Use

User wants to manage events from the macOS Calendar stack where Google, iCloud, Exchange, and CalDAV accounts are already synced locally. Agent handles lookup, create, update, delete, conflict checks, and post-write verification without provider OAuth setup.

Requirements

• macOS with Calendar app access enabled for terminal tools.
• At least one working command path: apple-calendar-cli, icalBuddy, shortcuts, or osascript.
• User confirmation before destructive operations.
• Provider accounts should already be connected in Calendar.app; this skill does not run provider OAuth.

Architecture

Memory lives in ~/apple-calendar-macos/. See memory-template.md for structure.

~/apple-calendar-macos/
├── memory.md                  # Status, defaults, and confirmation behavior
├── command-paths.md           # Detected CLI path and fallback status
├── timezone-defaults.md       # Preferred timezone and date style
└── safety-log.md              # Deletions, bulk edits, and rollback notes

Quick Reference

Data Storage

All skill files are stored in ~/apple-calendar-macos/. Before creating or changing local files, describe the planned write and ask for confirmation.

Core Rules

1. Treat Calendar.app as the Unified Calendar Source

• Assume provider sync already happens inside Calendar.app and operate on that local unified view.
• Do not request Google, Microsoft, or Apple OAuth inside this skill unless user explicitly asks for external setup help.

2. Detect Command Path Before Any Calendar Action

• Probe available tools in strict order: apple-calendar-cli, then icalBuddy, then shortcuts, then osascript.
• If no path is available, stop and explain the missing requirement instead of guessing commands.

3. Use Deterministic Time Inputs and Calendar Scopes

• Normalize all user time inputs to explicit timezone and start/end boundaries before running commands.
• Confirm date interpretation when input is ambiguous such as "next Friday" or locale specific formats.

4. Read First, Then Write, Then Verify

• For create, update, or delete operations, run a bounded pre-read in the target time window.
• After each write, run read-back verification and report final state with title, time, and calendar.