canvascoding/canvas-notebook / seed_skills/gccli
gccli
UnverifiedGoogle Calendar CLI for listing calendars, viewing/creating/updating events, and checking availability. Triggers: Google Calendar, calendar event, schedule meeting, check availability, create event, calendar freebusy, gccli.
Google Calendar CLI
Command-line interface for Google Calendar operations.
Installation
In Canvas Notebook Docker, a container admin installs this once:
npm install -g @mariozechner/gccli
Check if installed:
gccli --help
Setup
Google Cloud Console (one-time)
- Create a new project (or select existing)
- Enable the Google Calendar API
- Set app name in OAuth branding
- Add test users (all Gmail addresses you want to use)
- Create OAuth client:
- Click "Create Client"
- Application type: "Desktop app"
- Download the JSON file
Configure gccli
First check if already configured:
gccli accounts list
If no accounts, guide the user through setup:
- Ask if they have a Google Cloud project with Calendar API enabled
- If not, walk them through the Google Cloud Console steps above
- Have them download the OAuth credentials JSON
- Run:
gccli accounts credentials ~/path/to/credentials.json - Run:
gccli accounts add <email>(use--manualfor browserless OAuth)
Usage
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 availability
Use primary as calendarId for the main calendar.
Date/Time Format
- Timed events:
YYYY-MM-DDTHH:MM:SSZ(UTC) orYYYY-MM-DDTHH:MM:SS(local) - All-day events:
YYYY-MM-DDwith--all-dayflag
Data Storage
~/.gccli/credentials.json- OAuth client credentials~/.gccli/accounts.json- Account tokens
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 117k | Updated | Claude CodeCodex | Unverified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 107k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 107k | Updated | Claude CodeCodex | Verified | Install |