Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Access and manage Google Calendar events with gogcli for cross-calendar agendas, keyword search, and filtered outputs avoiding unwanted calendars like holidays.
Access and manage Google Calendar events with gogcli for cross-calendar agendas, keyword search, and filtered outputs avoiding unwanted calendars like holidays.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Use gog (gogcli) for Google Calendar: agenda (events list) and keyword search across calendars.
gogcli stdout should stay parseable; prefer --plain / --json and put hints to stderr. oai_citation:0‡GitHub Default to --plain for read-only listing you only summarize (cheaper tokens): agenda listing (today / next days / range) calendars list Use --json only when structure is required: aggregating results across calendars (cross-calendar keyword search) deduping / sorting / extracting IDs for follow-up calls any write workflow where exact fields matter In automation runs, add --no-input (fail instead of prompting). oai_citation:1‡GitHub
Users may explicitly exclude certain calendars from searches/agenda (e.g., “National holidays”). When answering, you MUST: Query broadly (e.g., events --all or iterate all calendars for search), Then filter out excluded calendars in post-processing. How to determine excluded calendars: First, check the user’s preferences/memory for an explicit “exclude calendars” list. If none is provided, apply a conservative default filter for obvious noise calendars: calendars whose name/summary contains: holiday, holidays, national holidays (and localized equivalents) Never filter out user-owned calendars unless explicitly excluded. Filtering rule: If you have calendar metadata (from gog calendar calendars), filter by calendar name/summary. If you only have events output, filter by matching event’s calendarId to the excluded calendarIds resolved from the calendars list. Always mention filtering briefly if it materially changes the answer: “(Filtered out: National holidays)”
For “what’s on my calendar today / tomorrow / this week / between X and Y”: MUST query all calendars: gog calendar events --all --from <date_or_iso> --to <date_or_iso> --plain Then apply calendar exclusions (above). Do not answer “nothing scheduled” unless you ran the command for the correct window and applied filtering. Examples: Today: gog calendar events --all --from 2026-02-04 --to 2026-02-05 --plain Next 7 days: gog calendar events --all --from 2026-02-04 --to 2026-02-11 --plain Output formatting: sort by start time group by day show: time range, summary, location (calendar name only if it helps)
Calendar event queries are scoped to a calendarId (API is /calendars/{calendarId}/events), so keyword search must iterate calendars and aggregate results. oai_citation:2‡Google for Developers Default window: if user didn’t specify a range: next 6 months from today (inclusive) if user specified date/range: use it Workflow (do not skip): List calendars (need IDs + names for filtering): gog calendar calendars --json Build the set of excluded calendarIds from the exclusions rule. For EACH non-excluded calendarId, search (JSON required for merge/dedupe): gog calendar search "<query>" --calendar <calendarId> --from <from> --to <to> --max 50 --json --no-input Aggregate all matches across calendars (do NOT stop on first match unless user asked). Deduplicate by (calendarId, eventId), sort by start time. Report results and explicitly mention the searched window (and any filters applied). If nothing found in default window: say: “No events found in the next 6 months (<from> → <to>). Want me to search further (e.g., 12 months) or within specific dates?” Fallback if user is sure it exists: ask/derive an approximate date and list around it (then filter): gog calendar events --all --from <date-7d> --to <date+7d> --plain then match by title tokens locally (casefold + token overlap)
Before any write action: summarize exact intent (calendar, title, start/end, timezone, attendees, location) ask for explicit “yes” then run the command
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.