ical
ReviewAudited by ClawScan on May 10, 2026.
Overview
The skill is coherently about managing Apple Calendar, but it gives agents broad calendar-changing power and explicitly tells non-interactive agents to bypass deletion prompts.
Install only if you trust the upstream ical CLI and are comfortable giving it Calendar access. Before letting an agent use it, set clear rules that destructive actions require your explicit approval, avoid --force except after approval, and use exact event IDs or freshly listed targets rather than stale row numbers.
Findings (5)
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.
An agent could delete calendar events without an interactive confirmation prompt if it acts on a wrong row number, misunderstood request, or stale context.
The skill explicitly encourages non-interactive agent/script deletion with --force, which bypasses the CLI's confirmation step for a destructive calendar operation.
Delete an event (--force skips confirmation prompt, required in scripts/agents)
Require explicit user confirmation before any delete, import, bulk update, or calendar deletion; use --id exact event identifiers and show the target event/calendar before using --force.
A mistaken calendar delete could remove many events at once, potentially affecting synced calendars such as iCloud if the chosen source is synced.
A single command can remove an entire calendar and all of its events, and the documented force flag skips confirmation.
Permanently delete a calendar and all its events... `--force` | `-f` | Skip confirmation prompt
Before deleting a calendar, list and confirm the exact calendar name/source, consider exporting a backup first, and do not let the agent use --force unless the user has clearly approved that exact destructive action.
The installed CLI is the component that will receive Calendar permissions, so changes in the upstream package could affect what code runs locally.
The install instruction pulls an external executable at a moving @latest version, while the reviewed skill artifacts do not include that code.
go install github.com/BRO3886/ical/cmd/ical@latest
Review the upstream repository before installing, pin a specific trusted version or commit where possible, and reinstall only when you intend to accept upstream changes.
Commands may read or change personal or work calendar data under the user's local Calendar/iCloud authority.
The tool operates through the user's macOS Calendar permissions and can work with account-backed sources such as iCloud, which is expected for the skill but sensitive.
A Go CLI that wraps macOS Calendar... ical calendars create "Projects" --source iCloud
Grant Calendar access only if you trust the installed CLI, and keep agent instructions scoped to the specific calendar and date range needed.
If the cache is stale or the agent uses an old row number, it may act on the wrong event.
The skill relies on a persistent local cache to map later row-number references to events, which can influence later show/update/delete actions.
Event listings display row numbers (`#1`, `#2`, `#3`...) alongside events. These are cached to `~/.ical-last-list` so you can reference them in subsequent commands
Refresh the list immediately before using row numbers, and prefer exact `--id` values for updates or deletions.