メニュー
Google Calendar CLI for listing calendars, viewing/creating/updating events, and checking availability.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | gccli |
| description | Google Calendar CLI for listing calendars, viewing/creating/updating events, and checking availability. |
Command-line interface for Google Calendar operations.
npm install -g @mariozechner/gccli
First check if already configured:
gccli accounts list
If no accounts, guide the user through setup:
gccli accounts credentials ~/path/to/credentials.jsongccli accounts add <email> (use --manual for browserless OAuth)Run gccli --help for full command reference.
Common operations:
gccli <email> calendars - List all calendarsgccli <email> events <calendarId> [--from <dt>] [--to <dt>] - List eventsgccli <email> event <calendarId> <eventId> - Get event detailsgccli <email> create <calendarId> --summary <s> --start <dt> --end <dt> - Create eventgccli <email> freebusy <calendarIds> --from <dt> --to <dt> - Check availabilityUse primary as calendarId for the main calendar.
YYYY-MM-DDTHH:MM:SSZ (UTC) or YYYY-MM-DDTHH:MM:SS (local)YYYY-MM-DD with --all-day flag~/.gccli/credentials.json - OAuth client credentials~/.gccli/accounts.json - Account tokensYYYY-MM-DD format with --all-day flag, not T00:00:00 timestampsprimary is the calendarId for the user's main calendar, not their email addressZ suffix are interpreted as local time, not UTCWeb search and content extraction via Brave Search API. Use for searching documentation, facts, or any web content. Lightweight, no browser required.
Interactive browser automation via Chrome DevTools Protocol. Use when you need to interact with web pages, test frontends, or when user interaction with a visible browser is required.
Create software architecture diagrams using the C4 model (Context, Containers, Components, Code). Applies Simon Brown's diagramming principles: titles, legends, directional arrows, explicit text, abstractions-first. Use when user asks for architecture diagrams, system diagrams, C4 diagrams, or wants to document software structure.
Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.
Query the cerebro cortex knowledge base for project context, journal entries, intent/goals, TODOs, and statistics. Use when the user asks about their projects, wants to read journal entries, check goals/intentions, search for TODOs across repos, or get an overview of their activity data. Also use when browsing what the user has been working on across their side projects.
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.