Apple Calendar (MacOS)

Use local CLI to manage Apple, Google, iCloud, Outlook, CalDAV, and other calendars synced in macOS Calendar, without API keys or OAuth.

Security Scan

The skill's requirements and instructions align with its stated purpose of managing calendars via local macOS tools; nothing in the bundle requests unrelated credentials or hidden network endpoints, though users should verify any third‑party binaries and review local files the skill will create.

Purpose & Capability

Name/description (manage calendars synced into macOS Calendar without OAuth) match the declared needs: a set of local CLI/tool fallbacks and a local config path. Requiring access to Calendar.app and local command-line tools is coherent for this purpose.

Instruction Scope

SKILL.md instructs the agent to probe local binaries, read before writing, request confirmations, and store small local state under ~/apple-calendar-macos/. It does not direct reading of unrelated system files, requesting unrelated credentials, or sending data to third‑party endpoints (the doc explicitly forbids that).

Install Mechanism

This is instruction-only (no install spec), which is lower risk. However the skill favors a third‑party tool named `apple-calendar-cli` as preferred path; the skill does not provide an install source. Users should verify the provenance and trustworthiness of any third‑party CLI they choose to install.

Credentials

No secrets or external API credentials are requested. The only declared config access is to ~/apple-calendar-macos/, which will store operation context, safety logs, and snapshots that may contain event metadata — this is proportionate but sensitive. Users should be aware that local calendar data (event titles/times/notes) may be written to that folder.

Persistence & Privilege

The skill is not always-on and is user-invocable; it requests no elevated platform privileges beyond typical terminal access to Calendar.app. It does not modify other skills or system-wide agent settings.

Assessment

This skill appears coherent with its purpose, but before installing or enabling it: 1) confirm which of the required CLIs you plan to use — especially `apple-calendar-cli` (verify its source and trustworthiness) — since the skill assumes those local tools exist but does not install them; 2) be prepared to grant your Terminal app Calendar access in macOS privacy settings so read/write operations work; 3) review the ~/apple-calendar-macos/ folder after first use — it will store operation context, safety logs, and snapshots that may include event details; 4) the skill explicitly says it will not send data to third‑party APIs, but if you later install or run an unknown third‑party CLI wrapper, that tool could change behavior, so only use CLIs you trust; 5) the agent will require explicit confirmation before destructive actions — pay attention to those prompts. If you want extra safety, avoid installing or enabling any non‑Apple CLIs and rely only on built‑in fallbacks (shortcuts/osascript/icalBuddy) or review the source of any third‑party binary before use.

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

Topic	File
Setup and first-run behavior	setup.md
Memory structure	memory-template.md
Command path matrix	command-paths.md
Safety checklist before writes	safety-checklist.md
Calendar operation patterns	operation-patterns.md
Troubleshooting and recovery	troubleshooting.md

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.

5. Confirm Destructive or Broad Changes

• Always require explicit confirmation for delete, move across calendars, and multi-event edits.
• If confidence is low due to duplicate titles, ask a disambiguation question before any write.

6. Keep Recurrence and All-Day Semantics Explicit

• Confirm recurrence rule, timezone behavior, and all-day interpretation before writing recurring events.
• Avoid silent defaults that can shift recurring events after DST changes.

7. Prioritize Minimal Exposure and Local-First Handling

• Use only the fields required for the requested action.
• Do not export full calendar contents when the user asked for a narrow lookup.
• Do not send event data to third-party APIs from this skill.

Common Traps

• Editing by title only when duplicates exist -> wrong event modified.
• Writing recurring events without timezone confirmation -> drift after DST.
• Deleting without pre-read snapshot -> difficult recovery.
• Trusting one CLI path blindly -> brittle behavior across macOS setups.
• Running broad searches by default -> noisy output and accidental edits.

Security & Privacy

Data that stays local:

• Calendar operation context and defaults in ~/apple-calendar-macos/.
• Event metadata used for requested operations.

Data that may leave your machine:

• None by default. Commands target local macOS Calendar data already synced on the device.

This skill does NOT:

• Request undeclared API keys.
• Send calendar data to third-party APIs.
• Execute destructive calendar writes without explicit confirmation.

Related Skills

Install with clawhub install <slug> if user confirms:

• macos - macOS workflows and system command patterns.
• events - event planning and structure patterns.
• meetings - meeting prep and follow-up workflows.
• schedule - broader scheduling and planning workflows.
• remind - reminder design and deadline management patterns.

Feedback

• If useful: clawhub star apple-calendar-macos
• Stay updated: clawhub sync