ClawHub

Apple Calendar CLI

v1.0.1

Manage Apple Calendar events on macOS 14+ using apple-calendar-cli: list, get, create, update, and delete events with ISO 8601 date support.

⭐ 2· 1.3k·3 current·4 all-time
by@sichengchen
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The name/description (manage Apple Calendar events) matches the runtime instructions: all commands operate on calendars/events via a local CLI that uses EventKit. There are no unrelated environment variables, binaries, or config paths requested.
✓
Instruction Scope
SKILL.md is narrowly scoped to running apple-calendar-cli commands (list, get, create, update, delete). It explicitly requires macOS Calendar permission (expected) and does not instruct the agent to read unrelated files, environment variables, or transmit data to external endpoints.
ℹ
Install Mechanism
This skill is instruction-only (no install spec). SKILL.md recommends: brew install sichengchen/tap/apple-calendar-cli — that is a third‑party Homebrew tap. Installing from a personal/unofficial tap can run arbitrary install scripts; consider vetting the tap or using an official release before installing.
✓
Credentials
No environment variables, credentials, or config paths are requested. The only required permission is macOS Calendar access (read/write) which is proportionate to managing calendars/events.
✓
Persistence & Privilege
The skill is not always-enabled and does not request persistent/global privileges or modify other skills. Agent autonomous invocation remains allowed by default, which is expected behavior and not a concern here by itself.
Assessment
This skill appears to do what it says: it runs a local CLI that uses macOS Calendar access. Before installing: (1) review the Homebrew tap (sichengchen/tap) or the tool's source — third‑party taps can execute install scripts; only install if you trust the author, (2) when granting Calendar permission, understand the tool can read and write your calendars and events, (3) test read-only commands first (list-calendars, list-events) to confirm behavior, and (4) if you prefer to avoid third‑party taps, look for an official release or build from source. No extra credentials are requested by the skill itself.

Like a lobster shell, security has layers — review code before you run it.

latestvk97bmyj8nz5hw0r5yev0ya4q6h81m68t

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments