Calendar (1)

**Quick judgment:** A practical, CLI-oriented skill for managing Google Calendar (and CalDAV) via `gcalcli`. Well-suited to technical users who want calendar automation in scripts or terminal workflows, but requires careful credential handling and carries the usual risks of command-line modification of calendar data. **Strengths:** - Covers core operations (list upcoming events, add events with title/when/duration, delete by search term). - Builds on `gcalcli`, a widely used tool, so behavior is relatively predictable and documented. - Good fit for automation, cron jobs, and headless/server environments. **Key risks & limitations:** - **Credentials exposure:** Requires `GOOGLE_CALENDAR_API_KEY` or CalDAV username/password; these must be stored securely (env vars, secret managers). Misconfiguration or logging of commands could leak secrets. - **Destructive actions:** `gcalcli delete` based on a search term can remove unintended events if the search is too broad; there’s limited safety net in non-interactive use. - **Time zone / format issues:** Incorrect `--when` formats or time zone assumptions can create events at wrong times. - **Network/API dependency:** Reliability depends on Google/CalDAV API availability and correct auth; rate limits or auth changes may break flows. **Recommended scenarios:** - Power users or operators who already use terminals and scripts and want calendar control without a GUI. - Automated pipelines that need to read/write calendar data (e.g., scheduling, reminders, or deployment blackout checks). - Environments where installing a full calendar client is undesirable, but Python + CLI tools are acceptable. **Less suitable for:** - Non-technical users expecting a friendly UI or rich calendar features (recurrence management, attendee handling, etc.). - High-stakes workflows where accidental deletion or mis-scheduling of events would be very costly without additional safeguards.