Apple Calendar Manager
PassAudited by ClawScan on May 10, 2026.
Overview
This skill appears purpose-aligned for adding Apple Calendar events, but users should note that it requires Calendar automation permission and references a missing AppleScript helper.
Before installing, confirm you are on macOS, review the missing add_event.scpt file if it is supplied separately, and allow Calendar automation only for calendar changes you explicitly want.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If invoked, the skill can add events to the user's Apple Calendar.
The script invokes AppleScript to control Apple Calendar and create an event. This is central to the stated purpose, but it is still a local automation action that changes user data.
osascript skills/apple-calendar-manager/add_event.scpt \
Only use it for explicit calendar changes and review the calendar name, title, dates, and times before allowing automation.
Granting automation access allows the skill's scripts to act on the user's Calendar app within the documented workflow.
The skill requires macOS automation permission to interact with the user's Calendar app. This is expected for the integration, but it is a meaningful permission boundary.
Apple Calendar application must be accessible and authorized for automation.
Grant Calendar automation permission only if you want OpenClaw to create calendar entries, and revoke it in macOS privacy settings if no longer needed.
The skill may fail as packaged, or any separately present add_event.scpt would determine the actual Calendar behavior without being included in this review.
The wrapper depends on add_event.scpt, but the provided manifest and file contents include only SKILL.md, add_event_smart.sh, and parse_relative_date.sh. The key AppleScript implementation is therefore not reviewable in the supplied artifacts.
osascript skills/apple-calendar-manager/add_event.scpt
Verify that add_event.scpt is present, matches the documented event-creation purpose, and contains no unexpected actions before running the wrapper.
