google-oauth-clilisted
Install: claude install-skill Z1Code/google-oauth-cli
# google-oauth-cli
Wrapper around a CLI. Never hand-edit console state; call the CLI.
## The rule
Run `gauth ...` and read the JSON. Do not try to drive the Cloud Console yourself,
and do not reach for `gcloud` for anything below — **the OAuth consent screen has no
API and no gcloud command**. `gcloud` only creates projects and enables APIs.
## Start here, always
```bash
gauth diagnose --project <id> --json
```
This is the single most useful call. It returns `blockers[]` with a stable `code`
you can branch on:
| `code` | Meaning |
|---|---|
| `NO_TEST_USERS` | Consent screen in Testing with zero test users → **every login is rejected before reaching the app** |
| `NOT_PUBLISHED` | App is in Testing, capped at 100 users for its entire lifetime |
| `BRANDING_URLS_MISSING` | Missing home page / privacy policy / terms → publishing is blocked |
| `BRANDING_CONTACT_MISSING` | Missing developer contact email |
`ok: true` with an empty `blockers` means the OAuth setup is not the problem — look
elsewhere.
## The two facts that matter most
**1. A consent screen in Testing with zero test users rejects every login, before the
request reaches the application.** Your app logs stay empty, so it looks like a code
bug. It is not. Fix:
```bash
gauth test-users add --project <id> --emails "a@x.com,b@y.com"
```
**2. Publishing requires a complete branding page**, including publicly reachable
privacy policy and terms URLs. If those pages do not exist on the site, publishing is
impossi