gws CLI: Shared Reference
Auth, global flags, output formats and security rules for the gws CLI
- What
- Auth, global flags, output formats and security rules for the gws CLI
- Cost
- Free
- Needs
- the `gws` binary on the PATH (see the repo README for install options); a Google account; either browser-based OAuth (`gws auth login`, interactive and free) or a Google Cloud service account key (set GOOGLE_APPLICATION_CREDENTIALS)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the shared reference every other `gws` skill builds on: browser-based OAuth (`gws auth login`) or service-account auth, the full method-flag syntax (`--params`, `--json`, `--page-all`, `--dry-run`, `--sanitize`), output formats (json, table, yaml, csv) and hard security rules (never output secrets, always confirm before writes, prefer `--dry-run` for destructive operations) — plus shell tips for quoting Sheet ranges and JSON in zsh. This is the prerequisite skill for the 8 sibling `gws-*` fiches listed in this lot (`gws-calendar`, `gws-tasks`, `gws-slides`, `gws-forms`, `gws-meet`, `gws-keep` and the calendar helpers) — install it first, not alone. Distinct from the 33 googleworkspace workflow/persona fiches of lot 31 (same repo, different skill family: this one documents the CLI itself, not its workflows). By @googleworkspace, listed here with credit to its creator. Honest caveats: not actionable on its own — it's auth and conventions; browser OAuth is interactive and free, service accounts require a Google Cloud project. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
gws CLI Shared Reference is a free Muse skill, the shared reference every other gws skill builds on. It covers browser-based OAuth or service-account auth, the full method-flag syntax for parameters, JSON output, paging, dry runs and sanitizing, plus output formats such as JSON, table, YAML and CSV, and hard security rules, including never outputting secrets.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit a3768d0Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: the `gws` binary on the PATH (see the repo README for install options); a Google account; either browser-based OAuth (`gws auth login`, interactive and free) or a Google Cloud service account key (set GOOGLE_APPLICATION_CREDENTIALS) Install "gws CLI: Shared Reference" for me. Give my agent the shared auth, flags, output-format and security rules for the gws CLI — the prerequisite reference for all gws-* skills Repository: https://raw.githubusercontent.com/googleworkspace/cli/a3768d0e82ad83cca2da97724e46bea4ff0e6dbd/skills/gws-shared/SKILL.md Pinned version: install the code at commit a3768d0e82ad83cca2da97724e46bea4ff0e6dbd exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file for the googleworkspace-cli-gws-shared skill from the repository into a temporary folder 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "googleworkspace-cli-gws-shared". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. install the gws binary, run `gws auth login`). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- a3768d0 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026 · Observed during the install test: registry.npmjs.org
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.