Google Calendar (via gogcli)
v1.0.0Access and manage Google Calendar events with gogcli for cross-calendar agendas, keyword search, and filtered outputs avoiding unwanted calendars like holidays.
⭐ 5· 5k·33 current·34 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
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.
Instruction Scope
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.
Install Mechanism
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.
Credentials
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.
Persistence & Privilege
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.
Assessment
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.Like a lobster shell, security has layers — review code before you run it.
agendavk970r1ej3vk7dyv2e66nkf03j580f85mcalendarvk970r1ej3vk7dyv2e66nkf03j580f85meventsvk970r1ej3vk7dyv2e66nkf03j580f85mgogclivk970r1ej3vk7dyv2e66nkf03j580f85mgoogle-calendarvk970r1ej3vk7dyv2e66nkf03j580f85mlatestvk970r1ej3vk7dyv2e66nkf03j580f85mproductivityvk970r1ej3vk7dyv2e66nkf03j580f85mschedulevk970r1ej3vk7dyv2e66nkf03j580f85m
License
MIT-0
Free to use, modify, and redistribute. No attribution required.