Access and manage Google Calendar events with gogcli for cross-calendar agendas, keyword search, and filtered outputs avoiding unwanted calendars like holidays.
Security Analysis
medium confidenceInstructions are consistent with a Google Calendar helper that uses the gogcli tool; nothing in the skill asks for unrelated credentials or to access unrelated system resources, but the skill assumes local gog authentication and a third‑party Homebrew tap which you should review before installing.
The name and SKILL.md describe using the gog (gogcli) command-line tool to list/search/create calendar events. The metadata declares the required binary ('gog') and an install recipe (Homebrew formula steipete/tap/gogcli) that matches the stated purpose.
Instructions tell the agent to run gog commands to list/search/modify calendars and to consult the user's preferences/memory for excluded calendars. This is within scope for a calendar skill. Note: the skill implicitly relies on the local gog authentication state (OAuth tokens) but does not document authentication steps or where tokens live.
No install spec in the package itself, but metadata suggests installing gogcli via a Homebrew formula from steipete/tap. Homebrew installs are common and expected, but this is a third-party tap — you should verify the upstream project (GitHub repo) and the formula before running it.
The skill declares no environment variables or config paths. However, to access Google Calendar the gog client will need OAuth credentials/tokens stored locally (or via the system). The SKILL.md does not mention these tokens or required scopes, so there's a minor coherence gap: the ability to actually access calendars depends on local auth state outside the skill's declarations. No unrelated secrets are requested by the skill.
Skill is not always-enabled and does not request elevated platform privileges. It is instruction-only and will execute gog commands when invoked; there is no indication it modifies other skills or system-wide settings.
Guidance
This skill appears to do what it says: run gogcli to read and (with confirmation) write Google Calendar data. Before installing or using it: 1) inspect the upstream gogcli project (https://github.com/steipete/gogcli) and the Homebrew formula to ensure you trust the tap; 2) be aware gog uses OAuth tokens stored locally — confirm which Google account will be accessed and what scopes are granted; 3) expect the agent to run gog commands that read your calendar content and only allow writes after explicit confirmation; and 4) if you later want to revoke access, remove gog's OAuth tokens or revoke access from your Google account security settings. If you want a tighter review, provide the exact Homebrew formula or your environment's authentication method so I can check where credentials are stored and what permissions gog requests.
Latest Release
v1.0.0
Initial release of the dedicated gog-calendar skill for cross-calendar agenda and keyword search via gogcli. - Provides reliable agenda listings (today/week/custom range) by querying all calendars and applying customizable exclusions (e.g., holidays). - Supports best-effort keyword search by iterating/aggregating across calendars, with structured output (plain or JSON as appropriate). - Optimizes output for token efficiency—defaults to --plain except when structure is required. - Post-filters unwanted calendars by name/summary (e.g., holidays), with user or default exclusion rules. - Requires explicit user confirmation before any calendar write/modification.
More by @lstpsche
Published by @lstpsche on ClawHub
