gws-install
Quick install of the Google Workspace CLI (gws) on an additional machine using existing OAuth credentials. Requires client_secret.json from a previous gws-setup. Use whenever the user wants to install gws on a new computer, reinstall after a fresh OS, configure a second workstation, or says 'install gws', 'gws on new machine', 'set up gws again'.
Profile →npx skills add jezweb/claude-skills --skill gws-install --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Google Workspace CLI — Quick Install Install `gws` on an additional machine using OAuth credentials from a previous setup. Produces an authenticated CLI with all agent skills ready to use. **Prerequisite**: The user must have `client_secret.json` from a previous `gws-setup` (or from Google Cloud Console). If they don't have it, use the `gws-setup` skill instead. ## Workflow ### Step 1: Pre-flight Checks ```bash which gws && gws --version ls ~/.config/gws/client_secret.json gws auth status ``` If already authenticated with the right scopes, skip to Step 4. ### Step 2: Install the CLI ```bash npm install -g @googleworkspace/cli gws --version ``` ### Step 3: Set Up Credentials Ask the user to provide their `client_secret.json`. Three options: **Option A — Paste the JSON content:** Ask the user to paste the JSON. Write it to `~/.config/gws/client_secret.json`: ```bash mkdir -p ~/.config/gws ``` Expected format: ```json { "installed": { "client_id": "...", "project_id": "...", "auth_uri": "https://accounts.google.com/o/oauth2/auth", "token_uri": "https://oauth2.googleapis.com/token", "client_secret": "...", "redirect_uris": ["http://localhost"] } } ``` **Option B — File path:** If the
- Workflow
- Step 1: Pre-flight Checks
- Step 2: Install the CLI
- Step 3: Set Up Credentials
- Step 4: Authenticate
- Step 5: Install Agent Skills
- Step 6: Verify
- Troubleshooting
- "Auth error — credentials missing or invalid" (exit code 2)
- Token expired
- Skills not appearing in Claude Code
- See Also
which gws && gws --version ls ~/.config/gws/client_secret.json gws auth status npm install -g @googleworkspace/cli gws --version mkdir -p ~/.config/gws cp /path/to/client_secret.json ~/.config/gws/client_secret.json export GOOGLE_WORKSPACE_CLI_CLIENT_ID="your-client-id" export GOOGLE_WORKSPACE_CLI_CLIENT_SECRET="your-client-secret" gws auth login -s gmail,drive,calendar,sheets,docs,chat,tasks 2>&1 | tee /tmp/gws-auth-output.txt
What does the gws-install skill do?
Quick install of the Google Workspace CLI (gws) on an additional machine using existing OAuth credentials. Requires client_secret.json from a previous gws-setup. Use whenever the user wants to install gws on a new computer, reinstall after a fresh OS, configure a second workstation, or says 'install gws', 'gws on new machine', 'set up gws again'.
How do I install it?
Run `npx skills add jezweb/claude-skills --skill gws-install --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jezweb/claude-skills, a repository with 954 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.