gog
Skill573 starsChanged 39 days agoMITView on GitHub
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
54 other projects use a version of this, 37 of them edited; most edited versions we compared are an older text (34 of 35).
How people change it
Most projects run an older version: 34 of 35 add nothing and lack rules this one has, most likely added since.
Of the 35 edited versions we compared: 34 are an older text, 1 made changes of their own.
Not in older versions
- Prefer an already-authorized host account: run the requested
gogcommand first. Enter setup only after an authentication error. Never ask for passwords, client secrets, or refresh tokens in chat.missing from 34 of 34 - When the Gateway host has no local browser display:missing from 34 of 34
- Prefer a live callback listener on the Gateway host. From the machine with the browser, forward the exact callback port (
ssh -L <port>:127.0.0.1:<port> user@gateway-host), open the authorization URLgogprints, and let the redirect complete on that …missing from 34 of 34 - When a live listener is unavailable, the operator picks one paste-mode path in a trusted shell on the Gateway host. Callback URLs must never enter chat or agent tool input:missing from 34 of 34
- Keep the same resolved config context across remote steps:
GOG_CONFIG_DIRtakes precedence over--home, which takes precedence overGOG_HOME. Also preserve--client, services/scopes, redirect URI, and consent options. …missing from 34 of 34 - If desktop keyring is unavailable, configure the file backend (
gog auth keyring file) and setGOG_KEYRING_PASSWORDin the Gateway environment so non-interactive agent/--no-inputruns can read tokens. …missing from 34 of 34 - Use
gog calendar colorsto see all available event colors (IDs 1-11)missing from 8 of 34 - Add colors to events with
--event-color <id>flagmissing from 8 of 34
Rules people drop
- Prefer an already-authorized host account: run the requested
gogcommand first. Enter setup only after an authentication error. Never ask for passwords, client secrets, or refresh tokens in chat.dropped by 1 of 1 - When the Gateway host has no local browser display:dropped by 1 of 1
- Prefer a live callback listener on the Gateway host. From the machine with the browser, forward the exact callback port (
ssh -L <port>:127.0.0.1:<port> user@gateway-host), open the authorization URLgogprints, and let the redirect complete on that …dropped by 1 of 1 - When a live listener is unavailable, the operator picks one paste-mode path in a trusted shell on the Gateway host. Callback URLs must never enter chat or agent tool input:dropped by 1 of 1
- Keep the same resolved config context across remote steps:
GOG_CONFIG_DIRtakes precedence over--home, which takes precedence overGOG_HOME. Also preserve--client, services/scopes, redirect URI, and consent options. …dropped by 1 of 1 - If desktop keyring is unavailable, configure the file backend (
gog auth keyring file) and setGOG_KEYRING_PASSWORDin the Gateway environment so non-interactive agent/--no-inputruns can read tokens. …dropped by 1 of 1
We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- zkManuel0123/CodexClawedited, first seen Nov 16, 2026
- metaspartan/cybaraedited, first seen Nov 15, 2026
- howells/skillstheir own version, first seen Nov 13, 2026
- DmacMcgreg/psibotedited, first seen Nov 8, 2026
- QVerisAI/QVerisBotedited, first seen Nov 1, 2026
- therapys/dotagentstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use taskflow-inbox-triage, openclaw-release-maintainer and 7 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AtomicBot-aiSkilltaskflow-inbox-triage
Also in 6 projects that use this
hkyutongSkillopenclaw-release-maintainer
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
Also in 4 projects that use this
jiulingyunSkillBlueBubbles
为Clawdbot构建或更新BlueBubbles外部通道插件(扩展包,REST发送/探测,webhook入站)。
Also in 16 projects that use this
seedprodSkillvoice-call
Start voice calls via the OpenClaw voice-call plugin.
Also in 16 projects that use this
AtomicBot-aiSkilltaskflow
Also in 6 projects that use this
seedprodSkillsession-logs
Search and analyze your own session logs (older/parent conversations) using jq.
Also in 15 projects that use this
- +2 more from seedprod
Other versions54 projects use a version of this.
Word for word · 9
- molt-bot/clawdbot★ 395k100% same
- steipete/warelay★ 395k100% same
- moltbot/clawdbot★ 395k100% same
- openclaw/openclaw★ 395k100% same
- steipete/clawdis★ 394k100% same
- moltbot/moltbot★ 394k100% same
- clawdbot/clawdbot★ 394k100% same
- OpenClawAndroid/openclaw-android-assistant★ 556100% same
- bighamx/openclaw-android-node-apk★ 57100% same
Edited · 37
- spinabot/brigade★ 11k95% same
- the-open-agent/openagent★ 5.7k96% same
- casibase/casibase★ 5.7k96% same
- linuxhsj/openclaw-zero-token★ 5.2k96% same
- Bitterbot-AI/bitterbot-desktop★ 2.5k88% same
- OpenBMB/EdgeClaw★ 1.2k96% same
- understudy-ai/understudy★ 46195% same
- AtomicBot-ai/atomicbot★ 32596% same
- QVerisAI/QVerisBot★ 18496% same
- HybridAIOne/hybridclaw★ 16260% same
27 more not listed
Wrote their own version · 8
- openclaw/gogcli★ 8.6ksame name
- steipete/gogcli★ 8.6ksame name
- therapys/dotagents★ 8same name
- howells/skills★ 5same name
- jholhewres/devclaw-skills★ 4same name
- chris-hendrix/ai-hub★ 2same name
- skytiger6724/qwen-skills★ 2same name
- thoitiettxl-cyber/Claw-II★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository107 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- extensions/AGENTS.mdAGENTS.md
- openclaw-android/AGENTS.mdAGENTS.md
- scripts/AGENTS.mdAGENTS.md
- test/AGENTS.mdAGENTS.md
- ui/AGENTS.mdAGENTS.md
- agent-transcriptSkill
- auto-qaSkill
- autoreviewSkill
- channel-message-flowsSkill
- clawdtributorSkill
- claw-scoreSkill
- clawsweeperSkill
- codex-app-paritySkill
- control-ui-e2eSkill
- crabboxSkill
- deslopSkill
- discord-clawdSkill
- discord-e2eSkill
- discord-user-postSkill
- discrawlSkill
- gitcrawlSkill
- graincrawlSkill
- notcrawlSkill
- openclaw-changelog-updateSkill
- openclaw-ci-limitsSkill
- openclaw-debuggingSkill
- openclaw-docker-e2e-authoringSkill
- openclaw-ghsa-maintainerSkill
- openclaw-live-updaterSkill
- openclaw-parallels-smokeSkill
- openclaw-pr-maintainerSkill
- openclaw-qa-testingSkill
- openclaw-refactor-docsSkill
- openclaw-release-validationSkill
- openclaw-repair-sweepSkill
- openclaw-secret-scanning-maintainerSkill
- openclaw-test-heap-leaksSkill
- openclaw-testingSkill
- openclaw-test-performanceSkill
- openclaw-updateSkill
- parallels-discord-roundtripSkill
- proof-videoSkill
- prototype-openclaw-tuiSkill
- release-openclaw-announcementSkill
- release-openclaw-ciSkill
- release-openclaw-macSkill
- release-openclaw-maintainerSkill
- release-openclaw-plugin-testingSkill
- security-triageSkill
- slack-e2eSkill
- slacrawlSkill
- tag-duplicate-prs-issuesSkill
- technical-documentationSkill
- telegram-e2e-userbotSkill
- test-auditSkill
- update-team-serverSkill
- verify-releaseSkill
- 1passwordSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 2 are distinctive, and 9 are very specific to this project.
0
Common
Most of the 43 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 27
Use gog for Gmail/Calendar/Drive/Contacts/Sheets/Docs.
- Very specific: line 29
Prefer an already-authorized host account: run the requested gog command first.
- Distinctive: line 39
When the Gateway host has no local browser display:
- Very specific: line 41
Prefer a live callback listener on the Gateway host.
- Distinctive: line 42
When a live listener is unavailable, the operator picks one paste-mode path in a trusted shell on the Gateway host.
- Very specific: line 45
Keep the same resolved config context across remote steps: GOG_CONFIG_DIR takes precedence over --home, which takes precedence over …
- Very specific: line 46
If desktop keyring is unavailable, configure the file backend (gog auth keyring file) and set GOG_KEYRING_PASSWORD in the Gateway …
- Very specific: line 79
Use gog calendar colors to see all available event colors (IDs 1-11)
- Very specific: line 80
Add colors to events with --event-color <id> flag
- Very specific: line 96
Prefer plain text. Use --body-file for multi-paragraph messages (or --body-file - for stdin).
- Very specific: line 99
Use --body-html only when you need rich formatting.
“Common” is measured: kept by at least 6 in 10 of the 43 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
gog
Use gog for Gmail/Calendar/Drive/Contacts/Sheets/Docs. Requires OAuth setup.
Prefer an already-authorized host account: run the requested gog command first. Enter setup only after an authentication error. Never ask for passwords, client secrets, or refresh tokens in chat.
Setup (once)
gog auth credentials /path/to/client_secret.jsongog auth add you@gmail.com --services gmail,calendar,drive,contacts,docs,sheetsgog auth list
Remote / headless Gateway hosts
When the Gateway host has no local browser display:
- Prefer a live callback listener on the Gateway host. From the machine with the browser, forward the exact callback port (
ssh -L <port>:127.0.0.1:<port> user@gateway-host), open the authorization URLgogprints, and let the redirect complete on that forwarded port. - When a live listener is unavailable, the operator picks one paste-mode path in a trusted shell on the Gateway host. Callback URLs must never enter chat or agent tool input:
--manual: the operator pastes the full redirect URL intogog's interactive prompt.--remote --step 1: printsauth_url(andstate_reused) then exits. After browser consent, the operator runs--remote --step 2 --auth-url <callback-url>in the trusted shell. A failedlocalhostpage load after consent is expected.
- Keep the same resolved config context across remote steps:
GOG_CONFIG_DIRtakes precedence over--home, which takes precedence overGOG_HOME. Also preserve--client, services/scopes, redirect URI, and consent options. Matching unexpired manual state may be reused (state_reused=true). - If desktop keyring is unavailable, configure the file backend (
gog auth keyring file) and setGOG_KEYRING_PASSWORDin the Gateway environment so non-interactive agent/--no-inputruns can read tokens.gog auth doctorreports when the password is missing. - Callback received is not the same as token stored. If token exchange or identity lookup fails behind a proxy, restart from step 1 after the operator approves scoped egress or proxy exceptions for the required Google endpoints. Do not bypass host network policy or reuse failed or expired state.
For diagnostics, inspect every entry reported by gog auth list --check; its exit status does not prove every stored token is valid. Likewise, inspect the status reported by gog auth doctor rather than relying only on its exit code.
Common commands
- Gmail search:
gog gmail search 'newer_than:7d' --max 10 - Gmail messages search (per email, ignores threading):
gog gmail messages search "in:inbox from:ryanair.com" --max 20 --account you@example.com - Gmail send (plain):
gog gmail send --to a@b.com --subject "Hi" --body "Hello" - Gmail send (multi-line):
gog gmail send --to a@b.com --subject "Hi" --body-file ./message.txt - Gmail send (stdin):
gog gmail send --to a@b.com --subject "Hi" --body-file - - Gmail send (HTML):
gog gmail send --to a@b.com --subject "Hi" --body-html "<p>Hello</p>" - Gmail draft:
gog gmail drafts create --to a@b.com --subject "Hi" --body-file ./message.txt - Gmail send draft:
gog gmail drafts send <draftId> - Gmail reply:
gog gmail send --to a@b.com --subject "Re: Hi" --body "Reply" --reply-to-message-id <msgId> - Calendar list events:
gog calendar events <calendarId> --from <iso> --to <iso> - Calendar create event:
gog calendar create <calendarId> --summary "Title" --from <iso> --to <iso> - Calendar create with color:
gog calendar create <calendarId> --summary "Title" --from <iso> --to <iso> --event-color 7 - Calendar update event:
gog calendar update <calendarId> <eventId> --summary "New Title" --event-color 4 - Calendar show colors:
gog calendar colors - 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>
Calendar Colors
- Use
gog calendar colorsto see all available event colors (IDs 1-11) - Add colors to events with
--event-color <id>flag - Event color IDs (from
gog calendar colorsoutput):- 1: #a4bdfc
- 2: #7ae7bf
- 3: #dbadff
- 4: #ff887c
- 5: #fbd75b
- 6: #ffb878
- 7: #46d6db
- 8: #e1e1e1
- 9: #5484ed
- 10: #51b749
- 11: #dc2127
Email Formatting
- Prefer plain text. Use
--body-filefor multi-paragraph messages (or--body-file -for stdin). - Same
--body-filepattern works for drafts and replies. --bodydoes not unescape\n. If you need inline newlines, use a heredoc or$'Line 1\n\nLine 2'.- Use
--body-htmlonly when you need rich formatting. - HTML tags:
<p>for paragraphs,<br>for line breaks,<strong>for bold,<em>for italic,<a href="url">for links,<ul>/<li>for lists. Example (plain text via stdin):
gog gmail send --to recipient@example.com \ --subject "Meeting Follow-up" \ --body-file - <<'EOF' Hi Name, Thanks for meeting today. Next steps: - Item one - Item two Best regards, Your Name EOF- Example (HTML list):
gog gmail send --to recipient@example.com \ --subject "Meeting Follow-up" \ --body-html "<p>Hi Name,</p><p>Thanks for meeting today. Here are the next steps:</p><ul><li>Item one</li><li>Item two</li></ul><p>Best regards,<br>Your Name</p>"
Notes
- Set
GOG_ACCOUNT=you@gmail.comto avoid repeating--account. - For scripting, prefer
--jsonplus--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).
gog gmail searchreturns one row per thread; usegog gmail messages searchwhen you need every individual email returned separately.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

