Apple Calendar CLI

This SKILL.md describes a reasonable Apple Calendar CLI, but there are a few red flags you should consider before installing or using it: - Metadata vs. instructions mismatch: the skill metadata does not declare required binaries or an install method, yet the documentation instructs you to run `accli` and to install `@joargp/accli` via npm. Ask the publisher for an explicit install spec or a verified homepage/source. - Unknown npm package: `npm install -g @joargp/accli` will fetch and run code from the public npm registry. Verify the package and its owner (inspect the package on npm, the repository, and recent versions) before globally installing. Look for signs of trust: GitHub repo, maintainer history, README, and no malicious postinstall scripts. - Global npm installs can run install scripts and modify system state. Prefer inspecting the package (or installing locally in a sandbox) before granting broad system-level installation. - Calendar access is local and requires macOS permissions; the skill does not ask for cloud credentials, which is appropriate. Still, be aware that the installed CLI will be able to read and modify your local calendar data if granted permission. If you want to proceed safely: request the package source or a signed binary, inspect the npm package contents (and postinstall scripts) before running, prefer a local/sandboxed install, and test in a non-production account. If the publisher cannot provide a trustworthy repository or explanation for the missing install metadata, treat the package with caution.