Google Workspace CLI (gog)

Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.

Security Scan

The skill is internally consistent: it documents a CLI for Google Workspace, requires the gog binary and OAuth credentials (as expected), and its instructions align with that purpose.

Purpose & Capability

Name/description match the runtime instructions: all commands are standard gog CLI usage for Gmail/Calendar/Drive/Contacts/Sheets/Docs. The only required binary is 'gog', which is appropriate for a CLI integration.

Instruction Scope

SKILL.md asks the user to run gog auth commands and to supply a client_secret.json (OAuth client credentials) and optionally set GOG_ACCOUNT. These are expected for a Google Workspace CLI. The SKILL.md does reference an env var (GOG_ACCOUNT) that is not listed in the skill's declared requires.env, but this is harmless informational guidance rather than unexpected data collection.

Install Mechanism

The registry contains no formal install spec (instruction-only), which is low-risk. SKILL.md metadata suggests a brew formula (steipete/tap/gogcli). A third-party brew tap is a plausible install path but merits verification of the tap/source before installing.

Credentials

The skill declares no required environment variables or credentials. It does require OAuth client credentials (client_secret.json) for Google APIs — this is proportionate and expected for access to Gmail/Drive/etc. No unrelated secrets or unrelated services are requested.

Persistence & Privilege

Skill is not always-enabled and does not request elevated or persistent platform privileges. It does not instruct modifying other skills or system-wide agent settings.

Assessment

This skill appears to do what it says: it expects the 'gog' binary and Google OAuth credentials to operate on Gmail, Calendar, Drive, Contacts, Sheets, and Docs. Before installing or using it, verify the gog binary's provenance (check the upstream project or GitHub repo linked from https://gogcli.sh), and be cautious when adding OAuth client credentials — treat client_secret.json as sensitive and restrict scopes to the minimum needed. If you install via the suggested brew tap (steipete/tap/gogcli), inspect that tap's source first (third‑party taps can install arbitrary code). Finally, be mindful that using the CLI can read and send email and access files — confirm before any send/create actions and limit access where possible.

gog

Use gog for Gmail/Calendar/Drive/Contacts/Sheets/Docs. Requires OAuth setup.

Setup (once)

• gog auth credentials /path/to/client_secret.json
• gog auth add [e-mail] --services gmail,calendar,drive,contacts,sheets,docs
• gog auth list

Common commands

• Gmail search: gog gmail search 'newer_than:7d' --max 10
• Gmail send: gog gmail send --to [e-mail] --subject "Hi" --body "Hello"
• Calendar: gog calendar events <calendarId> --from <iso> --to <iso>
• Drive search: gog drive search "query" --max 10
• Contacts: gog contacts list --max 20
• Sheets get: gog sheets get <sheetId> "Tab!A1:D10" --json
• Sheets update: gog sheets update <sheetId> "Tab!A1:B2" --values-json '[["A","B"],["1","2"]]' --input USER_ENTERED
• Sheets append: gog sheets append <sheetId> "Tab!A:C" --values-json '[["x","y","z"]]' --insert INSERT_ROWS
• Sheets clear: gog sheets clear <sheetId> "Tab!A2:Z"
• Sheets metadata: gog sheets metadata <sheetId> --json
• Docs export: gog docs export <docId> --format txt --out /tmp/doc.txt
• Docs cat: gog docs cat <docId>

Notes

• Set GOG_ACCOUNT=[e-mail] to avoid repeating --account.
• For scripting, prefer --json plus --no-input.
• Sheets values can be passed via --values-json (recommended) or as inline rows.
• Docs supports export/cat/copy. In-place edits require a Docs API client (not in gog).
• Confirm before sending mail or creating events.