gmail-setuplisted

Connect a Gmail account to this machine, and diagnose it when Gmail calls start failing. Use when the user wants to set up, connect, or authorize Gmail; when they add a second account; when they ask why email stopped working; or when any gmail command returns auth_required, auth_expired, scope_insufficient, client_invalid, or api_not_enabled. Covers the one-time Google Cloud project and OAuth client, the login flow, multiple accounts as profiles, and `gmail doctor`.
hec-ovi/gmail-skill · ★ 0 · AI & Automation · score 75

Install: claude install-skill hec-ovi/gmail-skill

# gmail-setup Gmail access here is OAuth against the user's own Google Cloud project. Nothing works until that project exists and consent has been granted once. **Run `gmail doctor` first, every time.** It checks the whole chain (runtime, OAuth client, token, scopes, egress, two live API calls) and every failing check names the exact command or console page that fixes it. Do not guess from an error message when one command gives you the diagnosis. ```bash gmail doctor # full check, exits 2 if anything failed gmail doctor --quick # local files only, no network gmail doctor --json # the Envelope, for programmatic checks ``` ## Is it already set up? ```bash gmail whoami # the account, live, or "not logged in" ``` ## First-time setup The Google Cloud half is a browser task the user has to do themselves. Point them at the "Google Cloud setup" section of the project README rather than retyping it; it is roughly ten minutes and produces one file. Two things that go wrong constantly and are worth stating up front: - The OAuth client must be application type **Desktop app**. A Web client has no loopback redirect and consent can never complete. `gmail doctor` fails the `oauth-client` check with this if they picked wrong. - The Cloud project must stay in **Testing** with the user added as a test user. Gmail's `gmail.modify` scope is "restricted", and a Published project with a restricted scope hard-blocks at consent with "Access bloc