gog

# gog Google Workspace through `gog`. This skill is the local account map and safety wrapper. Discover flags from the binary (`gog schema`, `gog <svc> --help`). Every invocation: ```bash export GOG_HOME="${GOG_HOME:-$HOME/.config/vd/gog}" # source "$GOG_HOME/env" if present ``` Never run a bare `gog` without `GOG_HOME`. Tokens then land in `~/.config/gogcli` and this skill cannot see them. ## Flags (prompt / skill args) ``` vd:gog --account <name> --user <person|sa> <gmail|drive|calendar|sheets|docs|auth> ... ``` | Flag | Values | Default | |---|---|---| | `--account` | any name in `$HOME/.config/vd/gog-accounts/` | none; required on writes, ask if missing | | `--user` | `person` (human mailbox, refresh token), `sa` (service account key) | `person` | Discover the configured accounts, never assume them: ```bash ls "$HOME/.config/vd/gog-accounts/"*.md # <account>.user.md / <account>.sa.md ``` Resolve to a `gog` CLI identity: `--user person` → `gog --account <account>`, `--user sa` → `gog --account <account>-sa`. Read `$HOME/.config/vd/gog-accounts/<account>.<user|sa>.md` before the first call. If that file is missing, stop and say so. Do not invent an email. `--user person` is the Gmail/Calendar/Sheets-as-you path. `--user sa` is only for Drive/Sheets already shared with that key. Never send mail as `--user sa`. ## Multi-organization architecture Keep each organization in an explicit identity boundary: ```text account registry -> named gog client -> Google Clou...