Your Apple Calendar, on any platform. iCloud Calendar skill via CalDAV (RFC 4791) — works on macOS/Linux, and Windows with env/keyring auth. Supports event C...
Security Analysis
high confidenceThis skill is internally consistent: it implements an Apple Calendar CalDAV CLI, only asks for an app-specific iCloud password (or keyring/keychain), and its files and runtime instructions match that purpose.
Name/description, README, SKILL.md, and the included Python CLI implementation consistently describe a CalDAV-based iCloud calendar client. Required binary (python3), required env var (APPLECAL_PASSWORD), and optional keyring/keychain use are appropriate for the stated functionality.
Runtime instructions direct the agent to run the bundled Python script with Apple ID and (optionally) APPLECAL_PASSWORD or keyring-backed credentials. The script legitimately accesses local files only when performing attachment uploads, and it uses the macOS 'security' command only as a fallback to read Keychain — behavior that matches the README/notes. There are no instructions to read or exfiltrate unrelated files or credentials.
No install spec in the registry (instruction-only skill) and the README asks the user to pip-install 'requests' (and optionally 'keyring'), which is proportional and expected. Nothing is downloaded from arbitrary URLs or extracted to disk by an installer.
Only APPLECAL_PASSWORD is required (primary credential). The script optionally honors APPLECAL_ATTACH_DIR and may consult keyring or macOS Keychain; these are justified by the functionality. No unrelated service credentials or broad environment access are requested.
The skill is not force-included (always: false) and does not request elevated or persistent system-wide privileges. It uses local credential stores (keyring/Keychain) and respects an environment-var-based auth flow; it does not modify other skills or global agent configuration.
Guidance
This skill appears to be what it claims: a local Python CLI that manages your iCloud calendar over CalDAV. Before installing, consider the following: - You will need an Apple app-specific password (set APPLECAL_PASSWORD) or store credentials in keyring/Keychain; if you do not want the script to read Keychain, prefer the environment-variable option. - The script communicates with caldav.icloud.com and will transmit calendar data and any attachments you upload. Only attach files you trust. The code enforces an extension allowlist and blocks common sensitive paths/names, but no filter is perfect — consider setting APPLECAL_ATTACH_DIR to confine uploads to a dedicated folder. - The README asks you to pip install 'requests' (and optionally 'keyring'). Verify dependencies come from trusted sources and run installs in a controlled environment (virtualenv) if you prefer. - The code uses subprocess.run('security', ...) on macOS to read Keychain when APPLECAL_PASSWORD is not set; this behavior is expected but means the binary will call a system utility to retrieve credentials. - The skill is user-invocable and may be called by an autonomous agent (normal platform behavior). If you are cautious about autonomous operations, restrict agent permissions or only invoke the skill manually. If you want higher assurance, review the full scripts/applecal.py source (included) to confirm there are no hidden network endpoints or unexpected logging/exfiltration before use.
Latest Release
v1.3.0
apple-cal-anywhere 1.3.0 - Adds support for managed attachments (RFC 8607), compatible with iPhone and iPad. - Enables querying multiple calendars in a single command for event listing. - Introduces free/busy lookup with event-derived fallback. - Enhances event update with options to explicitly clear location or description fields. - Improves attachment safety with allowlisted file extensions, sensitive path blocking, and optional directory scoping via APPLECAL_ATTACH_DIR. - Expands authentication fallback order and clarifies use of the APPLECAL_PASSWORD environment variable.
Popular Skills
Published by @xushen-ma on ClawHub
