
Gccli
- 138 installs
- 2.3k repo stars
- Updated June 6, 2026
- badlogic/pi-skills
Run and compose Google Cloud CLI commands for provisioning, IAM, deployments, and troubleshooting so agents can manage GCP resources without switching to ad-hoc shell scripts.
About
gccli from badlogic/pi-skills teaches Claude Code agents to execute structured Google Cloud CLI workflows for provisioning, IAM, deployments, and ops tasks, replacing fragile ad-hoc gcloud scripts with repeatable, reviewable infrastructure commands.
- Google Cloud CLI command patterns
- Project, IAM, and service management
- Deploy and troubleshoot GCP resources
- Agent-safe terminal workflows
- Reduces brittle one-off gcloud scripts
Gccli by the numbers
- 138 all-time installs (skills.sh)
- Ranked #513 of 1,039 Cloud & Infrastructure skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/badlogic/pi-skills --skill gccliAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 138 |
|---|---|
| repo stars | ★ 2.3k |
| Last updated | June 6, 2026 |
| Repository | badlogic/pi-skills ↗ |
What it does
Run and compose Google Cloud CLI commands for provisioning, IAM, deployments, and troubleshooting so agents can manage GCP resources without switching to ad-hoc shell scripts.
Files
Google Calendar CLI
Command-line interface for Google Calendar operations.
Installation
npm install -g @mariozechner/gccliSetup
Google Cloud Console (one-time)
1. Create a new project (or select existing) 2. Enable the Google Calendar API 3. Set app name in OAuth branding 4. Add test users (all Gmail addresses you want to use) 5. Create OAuth client:
- Click "Create Client"
- Application type: "Desktop app"
- Download the JSON file
Configure gccli
First check if already configured:
gccli accounts listIf 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 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