[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M698R1CWB8X7QAXD0HSYD1HF":3,"skill-same:01M698R1CWB8X7QAXD0HSYD1HF":54},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M698R1CWB8X7QAXD0HSYD1HF","gog",null,"Use the gog CLI when Google connectors lack an operation, shell automation needs stable JSON, or local Google auth needs inspection. Shared account, auth, output, and safety guidance for all gog service skills.","openclaw\u002Fgogcli","openclaw","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F252820863?v=4","01M698P3FSAZ6B4R928ZF19KPT","01M698PDKEJBN14VE6XHC5KJX6",8583,"MIT","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fgogcli\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgog\u002FSKILL.md",[],[5,18],"google","2026-11-10 10:12:30",false,"---\nname: gog\ndescription: \"Use the gog CLI when Google connectors lack an operation, shell automation needs stable JSON, or local Google auth needs inspection. Shared account, auth, output, and safety guidance for all gog service skills.\"\n---\n\n# gog\n\nUse `gog` when built-in Google connectors are missing a feature, when shell\nautomation needs stable JSON, or when you need to inspect local Google auth\nstate before acting.\n\n## Fast Path\n\n```bash\ngog --version\ngog auth list --check --json --no-input\ngog auth doctor --check --json --no-input\nGOG_HELP=agent gog --help\ngog schema --json\n```\n\n`GOG_HELP=agent` makes root help emit a compact automation contract and common\nread-only recipes; commands and behavior stay unchanged. Machine output,\nnon-interactive behavior, stable exit codes, command guards, and\nuntrusted-content wrapping apply across the CLI. `schema` exposes command\nsyntax, stable exit codes, and effective safety state for automation.\n\nFor JSON output projection, `--fields` is accepted as an alias for `--select` on\ncommands that do not define their own API field-mask `--fields`; commands with a\nlocal field-mask flag keep that command-specific meaning.\n\n`--results-only` unwraps the primary result before `--select` projects it. For\nlists, select item-relative fields: `--results-only --select id`. Dot paths do\nnot broadcast through nested arrays (`--select items.id` selects nothing).\nUnmatched object fields are omitted.\n\nPick the account explicitly for API work:\n\n```bash\ngog --readonly --account user@example.com gmail search 'newer_than:7d' --json --wrap-untrusted\n```\n\nPrefer `--json --wrap-untrusted` for agent parsing when reading Google content.\nHuman hints and progress should stay on stderr; stdout is for data.\n\n## Safety Rules\n\n- Do not print access tokens, refresh tokens, OAuth client secrets, or keyring\n  passwords.\n- If `GOG_KEYRING_PASSWORD` is provided by a shell startup file or service\n  environment, use the matching shell\u002Fentrypoint so `gog` can unlock the file\n  keyring non-interactively. Do not print the value.\n- In headless\u002Fservice agents, verify the service environment, not just the login\n  shell. `GOG_KEYRING_BACKEND=file`, `GOG_KEYRING_PASSWORD`, and `HOME` must be\n  present in the process that launches `gog`.\n- Use `--no-input` in automation so auth\u002Fkeyring prompts fail clearly.\n- Use `--dry-run` first where commands support it.\n- Use `--readonly` for tasks that must not mutate Google data; remove it only\n  for the exact write the user approved.\n- Destructive commands require `--force`; do not add it unless the user asked\n  for that exact mutation.\n- Use `--gmail-no-send` or `GOG_GMAIL_NO_SEND=1` unless sending mail is the\n  requested task.\n- For shared agent environments, prefer a baked readonly or agent-safe binary\n  from `docs\u002Fsafety-profiles.md`.\n\nRuntime command guards:\n\n```bash\ngog --readonly --enable-commands gmail.search,gmail.get --gmail-no-send \\\n  --account user@example.com gmail search 'from:example@example.com' --json\n\ngog --enable-commands drive.ls,docs.cat --disable-commands drive.delete \\\n  --account user@example.com drive ls --max 10 --json\n```\n\n## Auth\n\nOAuth setup is partly interactive. An agent can inspect and diagnose it, but a\nhuman normally completes browser consent:\n\n```bash\ngog auth credentials list\ngog auth add user@example.com --services all-user --force-consent\ngog auth remove user@example.com\n```\n\nDefault for existing human\u002Fuser OAuth reauth: preserve broad service access.\nBefore reauth, run `gog auth list --check --json --no-input` and inspect the\naccount's existing `services`. When replacing an expired or revoked token, do\nnot silently reduce scope; prefer `--services all-user --force-consent` unless\nthe user explicitly asks for narrower scopes.\n\n`all-user` excludes Google Ads (`ads`). Google can require passkey enrollment\nbefore granting the Ads scope, which blocks the whole consent flow, so do not\nadd `ads` to a routine reauth even when the old token had it. Request it only\nwhen the user needs Google Ads access, with `--services all-user,ads`.\n\nUse narrow services only for throwaway\u002Ftest accounts, service-specific bot\naccounts, explicit user requests, or scoped security experiments. Safety should\nnormally be enforced at command time with `--enable-commands`,\n`--disable-commands`, `--gmail-no-send`, dry-runs, and account selection, not by\nunder-scoping durable user auth.\n\nService accounts are Workspace-only and mainly fit Admin, Groups, Keep, and\ndomain-wide delegation flows; they do not solve consumer `@gmail.com` OAuth.\n\nFor OpenClaw\u002Fsystemd setups, run the diagnostic through the actual agent\nentrypoint after restarting the service:\n\n```bash\nopenclaw agent --agent main --message \\\n  'Run: gog auth doctor --check --no-input && gog gmail search \"newer_than:1d\" --max 1 --json'\n```\n\nIf this fails with `keyring.password` while the same `gog auth doctor` works in\nthe shell, fix the service or agent environment before reauthenticating.\n\n### Browser-Driven Reauth\n\nAn agent can complete this flow end to end when it can drive a signed-in\nbrowser. Consent still happens in a real browser; nothing here bypasses it.\n\nRun the CLI leg in a detached tmux session so it survives command boundaries:\n\n```bash\ntmux -L gog-auth new-session -d -s auth -x 200 -y 50\ntmux -L gog-auth send-keys -t auth \\\n  \"gog auth add user@example.com --services all-user --force-consent --timeout 15m\" Enter\n```\n\nCapture the consent URL with `-J`:\n\n```bash\ntmux -L gog-auth capture-pane -t auth -p -J -S - \\\n  | grep -oE 'https:\u002F\u002Faccounts\\.google\\.com[^ ]+' | tail -1 > \"$url_file\"\n```\n\n**`-J` is mandatory.** `capture-pane` otherwise returns the URL hard-wrapped at\nthe pane width. A truncated consent URL does not fail loudly: Google renders\n`Invalid OAuth Request` \u002F `Invalid response_type: missing`, which reads like a\nclient misconfiguration and sends you debugging the wrong thing. Verify the\ncaptured URL contains `response_type` before using it.\n\nWrite the URL to a mode-0600 file and use a browser automation tool that can\nread that file and open the consent URL without displaying it in logs; never\necho it. Appending `&login_hint=user@example.com`\nskips the account chooser and removes a whole class of wrong-account risk.\n\nExpect up to two interstitials when the OAuth client is unverified or in\ntesting:\n\n1. **\"Google hasn't verified this app.\"** `Continue` is a low-emphasis link on\n   one side; `Back to safety` is the prominent button. Activating the visually\n   obvious control aborts the flow. A developer-info control sits in the tab\n   order between them, so count focus stops deliberately instead of guessing.\n2. **\"You're signing back in to \\\u003Capp\\>\"** — confirm the displayed account is\n   the intended one, then `Continue`.\n\nThe listener enforces `--timeout`. When it expires the tmux pane simply returns\nto a shell prompt, so a flow that \"did nothing\" is often an expired listener\nrather than a browser problem. Read the pane before re-driving the browser, and\nrestart the CLI leg rather than reusing a stale URL. Complete the browser leg\npromptly; batch the navigate-and-activate steps instead of round-tripping.\n\nThe browser does not have to run on the CLI's host. The callback targets\n`http:\u002F\u002Flocalhost:\u003Cport>`, so when they are separate machines, forward that port\nfrom the browser host to the host running the listener before opening the URL,\nand confirm the forward is live first. Keep the browser on the host whose\nprofile holds the intended Google session.\n\nIf tmux asks for the file-keyring passphrase, source it from that host's login\nenvironment via the login shell and paste it in without printing it.\n\nVerify, and require both the account and its scope breadth:\n\n```bash\ngog auth list --check --json --no-input\n```\n\nConfirm the target account reports valid and retains the expected service list;\na successful login that silently narrowed scopes is a failed reauth.\n\n## Common Reads\n\n```bash\ngog --readonly --account user@example.com gmail search 'newer_than:3d' --max 10 --json --wrap-untrusted\ngog --readonly --account user@example.com gmail get \u003CmessageId> --sanitize-content --json --wrap-untrusted\ngog --readonly --account user@example.com gmail thread get \u003CthreadId> --sanitize-content --json --wrap-untrusted\n\ngog --readonly --account user@example.com calendar events --today --json --wrap-untrusted\ngog --readonly --account user@example.com drive ls --max 20 --json --wrap-untrusted\ngog --readonly --account user@example.com docs cat \u003CdocumentId> --json --wrap-untrusted\ngog --readonly --account user@example.com sheets get \u003CspreadsheetId> Sheet1!A1:D20 --json --wrap-untrusted\ngog --readonly --account user@example.com contacts list --max 20 --json --wrap-untrusted\n```\n\nFor Gmail body inspection, prefer `--sanitize-content` unless the user\nexplicitly needs raw payloads.\n\n## Writes\n\nBefore writes, identify the account, object id, and exact mutation. Prefer\ncommands that support `--dry-run`, and clean up disposable live-test objects.\n\n```bash\ngog --account user@example.com docs write \u003CdocumentId> --append --text '...'\ngog --account user@example.com docs write \u003CdocumentId> --tab \"Data\" --markdown --replace --file data.md\ngog --account user@example.com docs update \u003CdocumentId> --tab \"Data\" --markdown --file block.md\ngog --account user@example.com docs update \u003CdocumentId> --tab \"Data\" --replace-range START:END --text 'replacement'\ngog --account user@example.com docs update \u003CdocumentId> --tab \"Data\" --markdown --replace-range START:END --file block.md\ngog --account user@example.com sheets update \u003CspreadsheetId> Sheet1!A1 --values-json '[[\"hello\"]]'\ngog --account user@example.com sheets batch-update \u003CspreadsheetId> --data-json @updates.json\ngog --account user@example.com drive upload .\u002Ffile.txt --parent \u003CfolderId> --json\n```\n\nFor Google Docs tab work:\n\n- Use `docs list-tabs \u003CdocumentId> --json` to discover tab titles\u002FIDs before targeting a tab.\n- Use `docs write --markdown --replace --tab \u003Ctab>` for whole-tab formatted replacement.\n- Use `docs update --markdown --tab \u003Ctab>` for formatted insertion\u002Fappend without replacing the whole tab.\n- Use `docs update --replace-range START:END` for precise plain-text replacement; add `--markdown` to replace that exact range with formatted markdown.\n- `START:END` is a Google Docs UTF-16 API range. Resolve it from `docs cat --raw`, `docs raw`, or another `documents.get` readback; do not guess indexes.\n- `--replace-range` and `--index` are mutually exclusive.\n\nWhen testing creation commands, name artifacts with a clear temporary prefix and\ndelete or trash them after verification.\n\n`gmail batch delete` permanently deletes messages and requires the broader\n`https:\u002F\u002Fmail.google.com\u002F` OAuth scope. Prefer `gmail trash`; when permanent\ndeletion is required, follow the exact reauthorization command printed by `gog`.\n\nFor larger Sheets writes, prefer `sheets batch-update` over loops of\n`sheets update`; it sends multiple value ranges in one Sheets API request and\naccepts inline JSON or `@file` input.\n\nFor normal Gmail replies, use the first-class commands instead of rebuilding\nreply MIME through `gmail send`:\n\n```bash\ngog --account user@example.com gmail reply \u003CmessageId> --body-file reply.txt\ngog --account user@example.com gmail reply-all \u003CmessageId> --body-file reply.txt \\\n  --bcc introducer@example.com --remove former-participant@example.com\n```\n\nThey inherit the subject, quote by default, preserve display names and inline\nimages, and treat `--to`\u002F`--cc`\u002F`--bcc` as additive placement or moves. Use\n`--no-quote` to omit the original.\n\n## Discovery\n\nUse generated command docs and schema instead of guessing flags:\n\n```bash\ngog \u003Cservice> --help\ngog \u003Cservice> \u003Ccommand> --help\ngog schema \u003Cservice> \u003Ccommand> --json\n```\n\nDocs:\n\n- `docs\u002Findex.md`\n- `docs\u002Fcommands\u002FREADME.md`\n- `docs\u002Fagent-skills.md`\n- `docs\u002Fsafety-profiles.md`\n\nRepo paths:\n\n- CLI entrypoint: `cmd\u002Fgog\u002F`\n- Command implementations: `internal\u002Fcmd\u002F`\n- OAuth\u002Fkeyring: `internal\u002Fgoogleauth\u002F`, `internal\u002Fauthclient\u002F`, `internal\u002Fsecrets\u002F`\n- Generated command docs: `docs\u002Fcommands\u002F`\n","# gog\n\nUse `gog` when built-in Google connectors are missing a feature, when shell\nautomation needs stable JSON, or when you need to inspect local Google auth\nstate before acting.\n\n## Fast Path\n\n```bash\ngog --version\ngog auth list --check --json --no-input\ngog auth doctor --check --json --no-input\nGOG_HELP=agent gog --help\ngog schema --json\n```\n\n`GOG_HELP=agent` makes root help emit a compact automation contract and common\nread-only recipes; commands and behavior stay unchanged. Machine output,\nnon-interactive behavior, stable exit codes, command guards, and\nuntrusted-content wrapping apply across the CLI. `schema` exposes command\nsyntax, stable exit codes, and effective safety state for automation.\n\nFor JSON output projection, `--fields` is accepted as an alias for `--select` on\ncommands that do not define their own API field-mask `--fields`; commands with a\nlocal field-mask flag keep that command-specific meaning.\n\n`--results-only` unwraps the primary result before `--select` projects it. For\nlists, select item-relative fields: `--results-only --select id`. Dot paths do\nnot broadcast through nested arrays (`--select items.id` selects nothing).\nUnmatched object fields are omitted.\n\nPick the account explicitly for API work:\n\n```bash\ngog --readonly --account user@example.com gmail search 'newer_than:7d' --json --wrap-untrusted\n```\n\nPrefer `--json --wrap-untrusted` for agent parsing when reading Google content.\nHuman hints and progress should stay on stderr; stdout is for data.\n\n## Safety Rules\n\n- Do not print access tokens, refresh tokens, OAuth client secrets, or keyring\n  passwords.\n- If `GOG_KEYRING_PASSWORD` is provided by a shell startup file or service\n  environment, use the matching shell\u002Fentrypoint so `gog` can unlock the file\n  keyring non-interactively. Do not print the value.\n- In headless\u002Fservice agents, verify the service environment, not just the login\n  shell. `GOG_KEYRING_BACKEND=file`, `GOG_KEYRING_PASSWORD`, and `HOME` must be\n  present in the process that launches `gog`.\n- Use `--no-input` in automation so auth\u002Fkeyring prompts fail clearly.\n- Use `--dry-run` first where commands support it.\n- Use `--readonly` for tasks that must not mutate Google data; remove it only\n  for the exact write the user approved.\n- Destructive commands require `--force`; do not add it unless the user asked\n  for that exact mutation.\n- Use `--gmail-no-send` or `GOG_GMAIL_NO_SEND=1` unless sending mail is the\n  requested task.\n- For shared agent environments, prefer a baked readonly or agent-safe binary\n  from `docs\u002Fsafety-profiles.md`.\n\nRuntime command guards:\n\n```bash\ngog --readonly --enable-commands gmail.search,gmail.get --gmail-no-send \\\n  --account user@example.com gmail search 'from:example@example.com' --json\n\ngog --enable-commands drive.ls,docs.cat --disable-commands drive.delete \\\n  --account user@example.com drive ls --max 10 --json\n```\n\n## Auth\n\nOAuth setup is partly interactive. An agent can inspect and diagnose it, but a\nhuman normally completes browser consent:\n\n```bash\ngog auth credentials list\ngog auth add user@example.com --services all-user --force-consent\ngog auth remove user@example.com\n```\n\nDefault for existing human\u002Fuser OAuth reauth: preserve broad service access.\nBefore reauth, run `gog auth list --check --json --no-input` and inspect the\naccount's existing `services`. When replacing an expired or revoked token, do\nnot silently reduce scope; prefer `--services all-user --force-consent` unless\nthe user explicitly asks for narrower scopes.\n\n`all-user` excludes Google Ads (`ads`). Google can require passkey enrollment\nbefore granting the Ads scope, which blocks the whole consent flow, so do not\nadd `ads` to a routine reauth even when the old token had it. Request it only\nwhen the user needs Google Ads access, with `--services all-user,ads`.\n\nUse narrow services only for throwaway\u002Ftest accounts, service-specific bot\naccounts, explicit user requests, or scoped security experiments. Safety should\nnormally be enforced at command time with `--enable-commands`,\n`--disable-commands`, `--gmail-no-send`, dry-runs, and account selection, not by\nunder-scoping durable user auth.\n\nService accounts are Workspace-only and mainly fit Admin, Groups, Keep, and\ndomain-wide delegation flows; they do not solve consumer `@gmail.com` OAuth.\n\nFor OpenClaw\u002Fsystemd setups, run the diagnostic through the actual agent\nentrypoint after restarting the service:\n\n```bash\nopenclaw agent --agent main --message \\\n  'Run: gog auth doctor --check --no-input && gog gmail search \"newer_than:1d\" --max 1 --json'\n```\n\nIf this fails with `keyring.password` while the same `gog auth doctor` works in\nthe shell, fix the service or agent environment before reauthenticating.\n\n### Browser-Driven Reauth\n\nAn agent can complete this flow end to end when it can drive a signed-in\nbrowser. Consent still happens in a real browser; nothing here bypasses it.\n\nRun the CLI leg in a detached tmux session so it survives command boundaries:\n\n```bash\ntmux -L gog-auth new-session -d -s auth -x 200 -y 50\ntmux -L gog-auth send-keys -t auth \\\n  \"gog auth add user@example.com --services all-user --force-consent --timeout 15m\" Enter\n```\n\nCapture the consent URL with `-J`:\n\n```bash\ntmux -L gog-auth capture-pane -t auth -p -J -S - \\\n  | grep -oE 'https:\u002F\u002Faccounts\\.google\\.com[^ ]+' | tail -1 > \"$url_file\"\n```\n\n**`-J` is mandatory.** `capture-pane` otherwise returns the URL hard-wrapped at\nthe pane width. A truncated consent URL does not fail loudly: Google renders\n`Invalid OAuth Request` \u002F `Invalid response_type: missing`, which reads like a\nclient misconfiguration and sends you debugging the wrong thing. Verify the\ncaptured URL contains `response_type` before using it.\n\nWrite the URL to a mode-0600 file and use a browser automation tool that can\nread that file and open the consent URL without displaying it in logs; never\necho it. Appending `&login_hint=user@example.com`\nskips the account chooser and removes a whole class of wrong-account risk.\n\nExpect up to two interstitials when the OAuth client is unverified or in\ntesting:\n\n1. **\"Google hasn't verified this app.\"** `Continue` is a low-emphasis link on\n   one side; `Back to safety` is the prominent button. Activating the visually\n   obvious control aborts the flow. A developer-info control sits in the tab\n   order between them, so count focus stops deliberately instead of guessing.\n2. **\"You're signing back in to \\\u003Capp\\>\"** — confirm the displayed account is\n   the intended one, then `Continue`.\n\nThe listener enforces `--timeout`. When it expires the tmux pane simply returns\nto a shell prompt, so a flow that \"did nothing\" is often an expired listener\nrather than a browser problem. Read the pane before re-driving the browser, and\nrestart the CLI leg rather than reusing a stale URL. Complete the browser leg\npromptly; batch the navigate-and-activate steps instead of round-tripping.\n\nThe browser does not have to run on the CLI's host. The callback targets\n`http:\u002F\u002Flocalhost:\u003Cport>`, so when they are separate machines, forward that port\nfrom the browser host to the host running the listener before opening the URL,\nand confirm the forward is live first. Keep the browser on the host whose\nprofile holds the intended Google session.\n\nIf tmux asks for the file-keyring passphrase, source it from that host's login\nenvironment via the login shell and paste it in without printing it.\n\nVerify, and require both the account and its scope breadth:\n\n```bash\ngog auth list --check --json --no-input\n```\n\nConfirm the target account reports valid and retains the expected service list;\na successful login that silently narrowed scopes is a failed reauth.\n\n## Common Reads\n\n```bash\ngog --readonly --account user@example.com gmail search 'newer_than:3d' --max 10 --json --wrap-untrusted\ngog --readonly --account user@example.com gmail get \u003CmessageId> --sanitize-content --json --wrap-untrusted\ngog --readonly --account user@example.com gmail thread get \u003CthreadId> --sanitize-content --json --wrap-untrusted\n\ngog --readonly --account user@example.com calendar events --today --json --wrap-untrusted\ngog --readonly --account user@example.com drive ls --max 20 --json --wrap-untrusted\ngog --readonly --account user@example.com docs cat \u003CdocumentId> --json --wrap-untrusted\ngog --readonly --account user@example.com sheets get \u003CspreadsheetId> Sheet1!A1:D20 --json --wrap-untrusted\ngog --readonly --account user@example.com contacts list --max 20 --json --wrap-untrusted\n```\n\nFor Gmail body inspection, prefer `--sanitize-content` unless the user\nexplicitly needs raw payloads.\n\n## Writes\n\nBefore writes, identify the account, object id, and exact mutation. Prefer\ncommands that support `--dry-run`, and clean up disposable live-test objects.\n\n```bash\ngog --account user@example.com docs write \u003CdocumentId> --append --text '...'\ngog --account user@example.com docs write \u003CdocumentId> --tab \"Data\" --markdown --replace --file data.md\ngog --account user@example.com docs update \u003CdocumentId> --tab \"Data\" --markdown --file block.md\ngog --account user@example.com docs update \u003CdocumentId> --tab \"Data\" --replace-range START:END --text 'replacement'\ngog --account user@example.com docs update \u003CdocumentId> --tab \"Data\" --markdown --replace-range START:END --file block.md\ngog --account user@example.com sheets update \u003CspreadsheetId> Sheet1!A1 --values-json '[[\"hello\"]]'\ngog --account user@example.com sheets batch-update \u003CspreadsheetId> --data-json @updates.json\ngog --account user@example.com drive upload .\u002Ffile.txt --parent \u003CfolderId> --json\n```\n\nFor Google Docs tab work:\n\n- Use `docs list-tabs \u003CdocumentId> --json` to discover tab titles\u002FIDs before targeting a tab.\n- Use `docs write --markdown --replace --tab \u003Ctab>` for whole-tab formatted replacement.\n- Use `docs update --markdown --tab \u003Ctab>` for formatted insertion\u002Fappend without replacing the whole tab.\n- Use `docs update --replace-range START:END` for precise plain-text replacement; add `--markdown` to replace that exact range with formatted markdown.\n- `START:END` is a Google Docs UTF-16 API range. Resolve it from `docs cat --raw`, `docs raw`, or another `documents.get` readback; do not guess indexes.\n- `--replace-range` and `--index` are mutually exclusive.\n\nWhen testing creation commands, name artifacts with a clear temporary prefix and\ndelete or trash them after verification.\n\n`gmail batch delete` permanently deletes messages and requires the broader\n`https:\u002F\u002Fmail.google.com\u002F` OAuth scope. Prefer `gmail trash`; when permanent\ndeletion is required, follow the exact reauthorization command printed by `gog`.\n\nFor larger Sheets writes, prefer `sheets batch-update` over loops of\n`sheets update`; it sends multiple value ranges in one Sheets API request and\naccepts inline JSON or `@file` input.\n\nFor normal Gmail replies, use the first-class commands instead of rebuilding\nreply MIME through `gmail send`:\n\n```bash\ngog --account user@example.com gmail reply \u003CmessageId> --body-file reply.txt\ngog --account user@example.com gmail reply-all \u003CmessageId> --body-file reply.txt \\\n  --bcc introducer@example.com --remove former-participant@example.com\n```\n\nThey inherit the subject, quote by default, preserve display names and inline\nimages, and treat `--to`\u002F`--cc`\u002F`--bcc` as additive placement or moves. Use\n`--no-quote` to omit the original.\n\n## Discovery\n\nUse generated command docs and schema instead of guessing flags:\n\n```bash\ngog \u003Cservice> --help\ngog \u003Cservice> \u003Ccommand> --help\ngog schema \u003Cservice> \u003Ccommand> --json\n```\n\nDocs:\n\n- `docs\u002Findex.md`\n- `docs\u002Fcommands\u002FREADME.md`\n- `docs\u002Fagent-skills.md`\n- `docs\u002Fsafety-profiles.md`\n\nRepo paths:\n\n- CLI entrypoint: `cmd\u002Fgog\u002F`\n- Command implementations: `internal\u002Fcmd\u002F`\n- OAuth\u002Fkeyring: `internal\u002Fgoogleauth\u002F`, `internal\u002Fauthclient\u002F`, `internal\u002Fsecrets\u002F`\n- Generated command docs: `docs\u002Fcommands\u002F`\n",{"name":5,"description":7},"main","6d97417eade925947d721b4bb898815624310e44",".agents\u002Fskills\u002Fgog",731,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fgogcli","https:\u002F\u002Fgogcli.sh","https:\u002F\u002Fgithub.com\u002Fopenclaw","https:\u002F\u002Fopenclaw.ai","Your personal, open source AI assistant.","2026-11-14 12:06:09",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add openclaw\u002Fgogcli --skill gog",{"tool":40,"command":41},"bunx","bunx skills add openclaw\u002Fgogcli --skill gog",{"tool":43,"command":44},"pnpm","pnpm dlx skills add openclaw\u002Fgogcli --skill gog","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fgogcli\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgog\u002FSKILL.md",true,[48],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"agents\u002Fopenai.yaml","REFERENCE","参考文档",164,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fgogcli\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgog\u002Fagents\u002Fopenai.yaml",[55,63,72,80,93,101],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M698QZNQHT4T0H9BCP2JT8BW","gog-youtube","YouTube through gog. Use for YouTube search, videos, channels, activities, comments, playlists, and subscriptions.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fgogcli\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgog-youtube\u002FSKILL.md",[],[62],"gog youtube",{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M698QY3S7XNH2DVJWHBYBFPN","gog-weekly-digest","Read-only weekly digest across Google Calendar, Gmail, and Tasks with gog.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fgogcli\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgog-weekly-digest\u002FSKILL.md",[],[70,71,18],"gog weekly digest","gmail",{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M698QWN4REBTZ2T7NT01T57W","gog-tasks","Google Tasks through gog. Use for Google Tasks lists, task creation, updates, completion, and materialized repeats.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fgogcli\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgog-tasks\u002FSKILL.md",[],[79,18],"gog tasks",{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":91,"publishedAt":19},"01M698QV92FMM7ZY7MHGZ63M7P","gog-slides","Google Slides through gog. Use for presentations, slides, text, images, speaker notes, and exports.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fgogcli\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgog-slides\u002FSKILL.md",[86],{"categoryNo":87,"categoryName":88,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000003","演示文稿","SCENARIO","使用场景",[92,18],"gog slides",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M698QSNXVS0QAHB714914TQP","gog-sites","Google Sites through gog. Use for finding Google Sites in Drive, reading site metadata, and printing editor URLs; use gog-drive for file sharing.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fgogcli\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgog-sites\u002FSKILL.md",[],[100,18],"gog sites",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M698QR3D6VJ2ZXXFT1BEJ5QZ","gog-sheets","Google Sheets through gog. Use for spreadsheet cells, formulas, formatting, notes, validation, and sheet structure.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fgogcli\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgog-sheets\u002FSKILL.md",[],[108,18],"gog sheets"]