Calctl
v1.0.0Manage Apple Calendar events via icalBuddy + AppleScript CLI
⭐ 1· 2.6k·10 current·10 all-time
by@rainbat
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The SKILL.md clearly targets macOS (uses AppleScript/icalBuddy) and requires 'brew install ical-buddy', but the registry metadata lists no required binaries and no OS restriction. Asking to read and write a user's Calendar is coherent with the stated purpose, but the metadata omission is inconsistent and surprising.
Instruction Scope
The instructions focus on calendar operations (list/show/add/search) and mention using icalBuddy for reads and AppleScript for writes. They do not ask the agent to access unrelated files or external endpoints. However, the SKILL.md is purely descriptive (no concrete commands or implementation included) and contains example calendar names from a system — this may be benign sample data but is unexpected in a generic skill.
Install Mechanism
There is no install specification (lowest disk risk). Still, the documentation requires an external tool ('brew install ical-buddy'); that requirement is not reflected in metadata. Because installation is not automated by the skill, users will need to install ical-buddy and run on macOS themselves.
Credentials
The skill declares no environment variables or credentials (appropriate), but it will need access to the user's Calendar via AppleScript/osascript and likely Terminal automation permissions. Those sensitive access needs are not documented in the metadata (no platform/permission guidance), which is disproportionate to the registry's blank requirements.
Persistence & Privilege
The skill does not request always:true and uses default autonomous invocation settings. There is no evidence it requests persistent system-wide privileges or modifies other skills' configurations.
What to consider before installing
This skill appears to be a macOS-only CLI wrapper for Apple Calendar (reads via icalBuddy, writes via AppleScript), but the registry metadata does not declare macOS as a required platform or the ical-buddy dependency. Before installing or enabling it:
- Confirm you are on macOS and are comfortable granting Terminal/osascript automation access to control Calendar (Apple will prompt for these permissions). Calendar write access lets the skill create/modify events — consider privacy implications.
- Manually install and vet ical-buddy (brew install ical-buddy) from a trusted source before using. The skill does not include an install script, so installation happens outside the skill.
- Ask the skill author (or the registry) to update metadata to list required binaries and restrict the skill to macOS, and to provide exact commands the agent will run (so you can review them).
- Prefer skills with a homepage or source repository so you can inspect the implementation. If you cannot verify the origin, avoid granting automation/Calendar permissions.
I rated this 'suspicious' because the documentation and metadata are inconsistent and sensitive permissions (Calendar access) are implied but not documented; this could be benign oversight, but verify the points above before use.Like a lobster shell, security has layers — review code before you run it.
latestvk978fkd5yry2y5m1m1fc5st8xd7znz2d
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
