Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Google Calendar Agenda And Search

ASecurity

Use `gog` (gogcli) for Google Calendar: agenda (events list) and keyword search across calendars.

19 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsgogitapi

Works with

cliapi

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add rondoflow/rondoflow --skill google-calendar-agenda-and-search --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Google Calendar Agenda And Search?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Google Calendar Agenda And Search
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rondoflow-google-calendar-agenda-and-search/badge)](https://www.skillsdirectory.com/skills/rondoflow-google-calendar-agenda-and-search)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: google-calendar-agenda-and-search
description: "Use `gog` (gogcli) for Google Calendar: agenda (events list) and keyword search across calendars."
category: "Productivity"
author: community
version: "1.0.0"
icon: check-square
---

# gog-calendar

Use `gog` (gogcli) for Google Calendar: agenda (events list) and keyword search across calendars.

## Output rule (tokens vs reliability)

gogcli stdout should stay parseable; prefer `--plain` / `--json` and put hints to stderr.  [oai_citation:0‡GitHub](https://github.com/steipete/gogcli/blob/main/AGENTS.md?utm_source=chatgpt.com)

- 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](https://github.com/steipete/gogcli/blob/main/README.md?utm_source=chatgpt.com)

## Calendar exclusions (post-processing)

Users may explicitly exclude certain calendars from searches/agenda (e.g., “National holidays”).  
When answering, you MUST:
1) Query broadly (e.g., `events --all` or iterate all calendars for search),
2) 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)”

## Agenda (always cross-calendar, then filter)

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)

## Keyword search across calendars (best-effort, aggregate, then filter)

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](https://developers.google.com/workspace/calendar/api/v3/reference/events/list?utm_source=chatgpt.com)

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):
1) List calendars (need IDs + names for filtering):
   - `gog calendar calendars --json`
2) Build the set of excluded calendarIds from the exclusions rule.
3) 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`
4) Aggregate all matches across calendars (do NOT stop on first match unless user asked).
5) Deduplicate by `(calendarId, eventId)`, sort by start time.
6) 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)

## Writes (create/update/delete/RSVP)

Before any write action:
- summarize exact intent (calendar, title, start/end, timezone, attendees, location)
- ask for explicit “yes”
- then run the command

Attribution

rondoflowrondoflow
View sourceMore from rondoflow →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693161 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →