canvascoding/canvas-notebook / seed_skills/gccli
gccli
VerifiedGoogle 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.5 KB |
| agents/canvas.yaml | config | 204 B |
SKILL.md
View on GitHub---
name: gccli
description: "Google 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."
compatibility: Requires Google OAuth credentials configured via gccli setup
allowed-tools: Bash(gccli:*)
metadata:
version: "1.0"
author: canvas-studios
---
# Google Calendar CLI
Command-line interface for Google Calendar operations.
## Installation
In Canvas Notebook Docker, a container admin installs this once:
```bash
npm install -g @mariozechner/gccli
```
Check if installed:
```bash
gccli --help
```
## Setup
### Google Cloud Console (one-time)
1. [Create a new project](https://console.cloud.google.com/projectcreate) (or select existing)
2. [Enable the Google Calendar API](https://console.cloud.google.com/apis/api/calendar-json.googleapis.com)
3. [Set app name](https://console.cloud.google.com/auth/branding) in OAuth branding
4. [Add test users](https://console.cloud.google.com/auth/audience) (all Gmail addresses you want to use)
5. [Create OAuth client](https://console.cloud.google.com/auth/clients):
- Click "Create Client"
- Application type: "Desktop app"
- Download the JSON file
### Configure gccli
First check if already configured:
```bash
gccli accounts list
```
If no accounts, guide the user through setup:
1. Ask if they have a Google Cloud project with Calendar API enabled
2. If not, walk them through the Google Cloud Console steps above
3. Have them download the OAuth credentials JSON
4. Run: `gccli accounts credentials ~/path/to/credentials.json`
5. Run: `gccli accounts add <email>` (use `--manual` for browserless OAuth)
## Usage
Run `gccli --help` for full command reference.
Common operations:
- `gccli <email> calendars` - List all calendars
- `gccli <email> events <calendarId> [--from <dt>] [--to <dt>]` - List events
- `gccli <email> event <calendarId> <eventId>` - Get event details
- `gccli <email> create <calendarId> --summary <s> --start <dt> --end <dt>` - Create event
- `gccli <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) or `YYYY-MM-DDTHH:MM:SS` (local)
- All-day events: `YYYY-MM-DD` with `--all-day` flag
## 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: 119k | 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: 118k | Updated | Claude CodeCodex | Verified | 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: 108k | 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: 108k | Updated | Claude CodeCodex | Verified | Install |