2.5k
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
3 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill xferops-gog- _meta.json460 B
- SKILL.md5.1 KB
Overview
This skill is a Google Workspace CLI that provides command-line access to Gmail, Calendar, Drive, Contacts, Sheets, and Docs. It is designed for scripting, automation, and interactive use with OAuth-based authentication. It supports search, read, send, calendar event management, Drive queries, contacts listing, Sheets reads/updates, and Docs export/cat.
How this skill works
Install and perform a one-time OAuth setup with your client_secret.json, then add accounts and services you need. The CLI exposes subcommands for each Google service (gmail, calendar, drive, contacts, sheets, docs) and accepts flags for JSON output, formatting, and non-interactive operation. It supports headless environments via a keyring password or file keyring and environment variables to simplify scripting.
When to use it
- Automating mailbox operations: search, download attachments, create drafts, or send messages from scripts or cron jobs.
- Managing calendar events programmatically: list, create, update events, and apply event colors.
- Bulk Drive and Contacts queries for backups, audits, or migrations.
- Reading and writing Sheets data from automation pipelines using JSON value payloads.
- Exporting or previewing Docs content for backups or text processing.
Best practices
- Run gog auth once and set GOG_ACCOUNT to avoid repeating --account for every command.
- Use --json and --no-input for reliable scripting and parsing of results.
- Prefer --body-file (or stdin) for multi-paragraph email bodies; use --body-html only when needed.
- On headless servers set GOG_KEYRING_PASSWORD or use gog auth keyring file for non-interactive auth storage.
- For Sheets updates, provide values with --values-json and set --input USER_ENTERED when you want user-style parsing.
Example use cases
- Daily backup script: search Drive, export Docs as txt, and save attachments from recent Gmail messages to a storage bucket.
- CI pipeline step: run gog sheets get to verify test data, then append results with gog sheets append --values-json.
- Support automation: gog gmail messages search to fetch individual emails, then download attachments for ticket processing.
- Calendar automation: create recurring events with gog calendar create and set visual color using --event-color.
- Headless server reporting: run scheduled gog gmail search --max 10 --json and post results to a monitoring endpoint.
FAQ
Set GOG_KEYRING_PASSWORD in the environment or use gog auth keyring file; add the password to the systemd Environment for services.
How can I ensure scripts run without prompts?
Use --no-input and request JSON output with --json. Preconfigure GOG_ACCOUNT and ensure credentials are stored in the keyring or file.