Aj Gog

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

Security Scan

The skill is internally consistent with a Google Workspace CLI: it requires the gog binary, documents OAuth client credentials usage, and its install uses a Homebrew formula — nothing in the instructions or metadata indicates covert or unrelated access.

Purpose & Capability

Name/description match the runtime instructions. The skill expects the gog CLI and describes Gmail/Calendar/Drive/Contacts/Sheets/Docs commands; requiring the gog binary is proportional to the stated purpose.

Instruction Scope

SKILL.md only tells the agent to run gog commands and how to set up OAuth; it does not instruct reading unrelated system files or sending data to unexpected endpoints. It explicitly notes to confirm before sending mail or creating events.

Install Mechanism

Install uses a Homebrew formula (steipete/tap/gogcli) which is a typical installer path for CLI tools. This is moderate-low risk overall, but the tap is a third-party tap (not the official Homebrew/core), so users may want to inspect the formula before installing.

Credentials

The skill declares no required env vars in metadata, but SKILL.md references OAuth client_secret.json and suggests setting GOG_ACCOUNT. Requesting OAuth credentials and an account is expected for a Google Workspace CLI, but the metadata does not declare these config needs explicitly — users should be aware that sensitive credentials and tokens will be used/stored by the gog tool.

Persistence & Privilege

No elevated persistence requested (always:false). The skill does not request changes to other skills or global agent settings. Autonomous invocation is allowed by default, which is normal.

Assessment

This skill appears to do what it says: it is just wrappers around the gog CLI. Before installing: (1) review the Homebrew formula in steipete/tap to ensure you trust the maintainer; (2) be prepared to supply an OAuth client_secret.json from the Google Cloud Console and an account — these are sensitive and will allow the CLI to access your Gmail/Drive/etc.; (3) inspect where gog stores tokens on disk and revoke tokens if you later distrust the tool; and (4) when scripting, prefer the --no-input and --json options and confirm before using commands that send mail or modify data.

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.