iCalendar Sync

Use this skill to perform iCloud calendar CRUD operations from OpenClaw agents.

1. Prepare Credentials Securely

Use App-Specific Passwords only (never the primary Apple ID password).

Prefer keyring storage:

CODEBLOCK0

Use non-interactive setup for automation:

CODEBLOCK1

Use file storage only when keyring is unavailable (headless or GUI-restricted runtime):

CODEBLOCK2

2. Choose Provider Deliberately

• - --provider auto: macOS uses native bridge, non-macOS uses CalDAV.
• INLINECODE1: force direct iCloud CalDAV.
• INLINECODE2: force Calendar.app bridge (macOS only).

For CalDAV diagnostics, add:

CODEBLOCK3

3. Execute Calendar Operations

List calendars:

CODEBLOCK4

Get events:

CODEBLOCK5

Create event:

CODEBLOCK6

Update event (simple):

CODEBLOCK7

Update recurring event instance:

CODEBLOCK8

Modes for recurring updates:

• - single: update one instance (use --recurrence-id)
• INLINECODE5: update whole series
• INLINECODE6: split series and update this+future (use --recurrence-id)

Delete event:

CODEBLOCK9

4. Input Contract

For create, require at least:

• - summary (string)
• INLINECODE10 (ISO datetime)
• INLINECODE11 (ISO datetime, must be later than dtstart)

Optional fields:

• - INLINECODE13
• INLINECODE14
• INLINECODE15
• INLINECODE16 (0-9)
• INLINECODE17
• INLINECODE18

5. Safety Rules

• - Validate calendar names; reject path-like payloads.
• Keep credential material out of logs/output.
• Prefer keyring over file storage.
• If file storage is used, enforce strict file permissions (0600).

6. Failure Handling

If CalDAV auth/network fails on macOS and provider is auto/caldav, switch to macos-native and retry the same operation.

If JSON payload is supplied as file path, ensure file size stays within safe limits before parsing.