gmail-oauth
por kai-jar
DevOps & CloudResumo
Set up Gmail API access via gog CLI with manual OAuth flow.
Descrição
O que esta skill faz
Sets up Gmail API access using the `gog` CLI with a headless-compatible OAuth flow. Handles credential configuration, token exchange, and common authentication errors for personal or server-side Gmail integrations.
The `gog` CLI with file-based keyring makes OAuth token management work on headless servers where browser-based flows are impractical.
Quando usá-la
- Authorizing Gmail access on a headless server
- Renewing expired OAuth tokens without a browser on the server
- Setting up Gmail API for a personal automation script
- Troubleshooting OAuth errors like invalid_grant or redirect_uri_mismatch
- Configuring Gmail integration for a self-hosted email tool
Exemplo de fluxo de trabalho
User asks: set up Gmail OAuth on my headless server
- 1
Install gog CLI via brew and create a Google Cloud project with Gmail API enabled
- 2
Download OAuth client secret JSON (Desktop app type) from Google Cloud Console
- 3
Run
gog auth credentialswith the JSON file and configure file-based keyring - 4
Generate the OAuth URL, open it in a desktop browser, approve permissions, and copy the auth code
- 5
Exchange the code immediately using the auth script and verify access with a test search
Gmail API access configured with a permanent refresh token stored in file-based keyring
Requisitos
- Google Cloud project with Gmail API enabled
- OAuth 2.0 client credentials JSON file (Desktop app type) from Google Cloud Console
- gog CLI (`brew install steipete/tap/gogcli`)
- GOG_KEYRING_PASSWORD environment variable
Instalação
clawhub install kai-jar/gmail-oauthExecute o comando da CLI ou cole o prompt no Claude Code, Cursor, Codex ou no agente de código que você usa.