Apple Calendar CLI Plus

AdvisoryAudited by Static analysis on May 5, 2026.

Overview

No suspicious patterns detected.

Findings (0)

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.

What this means

An agent could accidentally change or delete important calendar events if used without review.

Why it was flagged

The CLI can update or delete calendar events, including whole recurring series. This is expected for a calendar-management tool, but it is a high-impact action if the agent targets the wrong event.

Skill content
`--span all` — all occurrences (deletes/updates the entire series)
Recommendation

Use `--dry-run`, stable calendar IDs, and explicit user confirmation before any update, delete, or recurring-series operation.

What this means

The installed CLI may be able to read and modify private calendar data available to Apple Calendar.

Why it was flagged

The skill requires macOS Calendar Full Access, which can expose and modify calendar data. This is disclosed and aligned with the stated calendar-management purpose.

Skill content
`accli setup` to grant Calendar permissions (Full Access required in System Settings > Privacy & Security > Calendars).
Recommendation

Grant Calendar access only if you trust the installed CLI, and revoke it in macOS Privacy settings when no longer needed.

What this means

The scanned skill text looks coherent, but the actual CLI behavior depends on an external package that was not reviewed here.

Why it was flagged

The skill depends on an external globally installed npm package, but the package code is not included in the provided artifacts and the registry has no install spec.

Skill content
requires:
  binaries: [accli]
  install: "npm install -g @gopaljigaur/accli"
Recommendation

Verify the npm package source and publisher before installing, and prefer pinned or reviewed versions where possible.

What this means

Private calendar information could be included in agent context, logs, or downstream outputs if broad exports are requested.

Why it was flagged

The export and search commands can place broad calendar details into agent-readable JSON output. This is purpose-aligned but may include sensitive event titles, locations, descriptions, and schedules.

Skill content
`accli export --from <date> --to <date> [--calendar-id <id>] [--json]` ... Exports all events grouped by calendar.
Recommendation

Limit exports/searches by date range and calendar ID, and avoid sending unnecessary calendar data into agent workflows.