thayyilshihab
v1.0.0Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
⭐ 0· 41·0 current·0 all-time
byDevilss Double@thayyilshihab24·duplicate of @jacobo-create/backup-gog-20260213-121122·canonical: @steipete/gog
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the runtime instructions and the declared required binary (gog). The SKILL.md shows only standard Gmail/Calendar/Drive/Sheets/Docs operations that the gog CLI would provide.
Instruction Scope
Runtime instructions stay within the tool's scope: they tell the agent how to perform OAuth setup (client_secret.json), authenticate accounts, and run gog commands. There are no instructions to read unrelated system files, harvest other credentials, or post data to unexpected endpoints.
Install Mechanism
Install is via a third‑party Homebrew tap (steipete/tap/gogcli) which creates the gog binary — this is a common and reasonable install method but is higher risk than a mainline homebrew/core formula. Recommend reviewing the tap/formula before installing.
Credentials
The skill declares no required env vars, which is consistent with being a CLI wrapper. However, SKILL.md requires an OAuth client_secret.json file and mentions an optional GOG_ACCOUNT env var; those credential/file requirements are reasonable for a Google Workspace CLI but are not reflected in 'required env vars'. Users should be aware that OAuth client secrets and access tokens will be used/stored by the gog tool.
Persistence & Privilege
The skill does not request always:true, does not modify other skills' config, and uses the normal agent invocation model. No elevated persistence or cross-skill access is requested.
Assessment
This skill appears to be a thin wrapper around the gog CLI. Before installing: 1) review the Homebrew tap formula (steipete/tap/gogcli) to confirm its source and contents; 2) be prepared to supply Google OAuth client credentials (client_secret.json) and to grant the gog tool access to Gmail/Drive/Calendar/etc — only grant the minimum scopes needed; 3) check where gog stores OAuth tokens on disk and ensure you’re comfortable with that storage location; 4) avoid using broad account credentials; and 5) test commands with read-only queries before using actions that send mail or create events. If you need higher assurance, verify the gog project homepage/repo and the brew formula source prior to installation.Like a lobster shell, security has layers — review code before you run it.
latestvk972a0banygr6zafhncdghgkzd83zdt0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🎮 Clawdis
Binsgog
Install
Install gog (brew)
Bins: gog
brew install steipete/tap/gogcli