Google Calendar (via gogcli)

**Overall**: Strong, well-thought-out Google Calendar integration via gogcli, especially suited for agents and automations that need cross-calendar agendas and keyword search. Good separation between plain-text (cheap summarization) and JSON (structured automation) flows. **Strengths** - Cross-calendar agenda listing with clear guidance to always query broadly (`--all`) and then apply post-processing filters. - Sensible calendar exclusion rules (e.g., holiday calendars), with explicit protection against accidentally hiding user-owned calendars. - Solid aggregation strategy for keyword search: list calendars, build exclusion set, per-calendar search, then dedupe/sort. - Automation-friendly design: `--no-input` to avoid interactive prompts; default 6‑month search window; explicit instructions on when JSON is required. **Risks / Limitations** - Depends on gogcli and Google Calendar API availability and configuration; misconfigurations or auth issues will surface as failures outside the skill’s direct control. - Cross-calendar search requires multiple API calls (one per calendar), which may incur latency for users with many calendars or hit rate limits in very large org setups. - Calendar data is inherently sensitive; while the skill is careful about confirmations for writes and noisy-calendar filtering, any usage must still respect privacy and data-handling policies. **Best-fit scenarios** - Personal or team assistants that need to answer “what’s on my calendar” or “find this kind of meeting” reliably across multiple calendars. - Workflow automations that aggregate events, dedupe across calendars, and then trigger follow-up actions (notifications, reports, scheduling logic). - Agents that must safely perform or propose calendar modifications while confirming exact intent (calendar, title, times, attendees) before issuing write commands.