Gmail OAuth Setup

**Judgement:** This skill is a strong, practical guide for setting up Gmail OAuth with the `gog` CLI, especially on headless servers. It’s well-structured, covers the full lifecycle from project setup to verification, and includes detailed troubleshooting for real-world Google OAuth quirks. **Key strengths:** - End-to-end, actionable steps with a dedicated helper script (`scripts/gmail-auth.sh`). - Tailored for headless and automation scenarios using file-based keyrings. - Comprehensive troubleshooting of common Google Cloud/OAuth issues (testing vs published app, verification warnings, redirect mismatches, token expiry, mobile redirects). - Sensible defaults around scopes (e.g., `gmail.modify`) and redirect URIs (`http://localhost`). **Risks & limitations:** - Relies on the `gog` CLI and Google Cloud Console; users must be comfortable with both. - OAuth flow is still manual and time-sensitive (auth codes expiring in minutes), so human error can cause frustration. - File-based keyring plus storing the keyring password in shell config has security implications if the system is compromised. - Instructions are Gmail- and `gog`-specific; not a general-purpose OAuth abstraction. **Recommended scenarios:** - You’re setting up Gmail access for automation scripts or tools that use `gog`, particularly on servers or remote machines. - Existing Gmail OAuth tokens for `gog` have expired or broken and you need a reliable recovery path. - You repeatedly hit Google OAuth issues (7-day tokens, verification warnings, redirect errors) and want a documented, battle-tested flow. - You need a minimal-scope, personal-use Gmail integration without going through full Google app verification.