gws-shared
by googleworkspacegws-shared is the shared reference for gws workflow automation, covering authentication, global flags, safe output formatting, and CLI command patterns.
This skill scores 78/100 because it gives agents a clear, reusable reference for the gws CLI’s shared mechanics: auth, global flags, syntax, and safety rules. For directory users, that means it is worth installing if they need a structured baseline for operating gws with less guesswork than a generic prompt, though it is more of a shared foundation than a complete task-specific workflow skill.
- Clear operational baseline: it documents authentication options, global flags, and core CLI syntax in one place.
- Agent-safe guidance is explicit, including dry-run usage, confirmation before destructive actions, and secret-handling rules.
- Good triggerability for the shared layer: frontmatter is valid, the skill has a concrete description, and the body includes actionable command examples.
- It is a shared reference rather than a full workflow skill, so users may still need other task-specific skills for end-to-end jobs.
- No install command or supporting scripts/references are included in the skill folder, which limits turnkey adoption and deeper automation.
Overview of gws-shared skill
What gws-shared is for
The gws-shared skill is the common layer for gws workflow automation: it helps you use shared authentication, global flags, and output handling consistently across Google Workspace CLI tasks. It is most useful if you want repeatable command patterns instead of inventing ad hoc prompts each time.
Who should install it
Install the gws-shared skill if you are building scripts, agents, or operator workflows around gws and need a reliable reference for login, service-account auth, pagination, dry runs, and safe output formatting. It is less useful if you only need one-off CLI commands and do not plan to reuse the pattern.
What it changes in practice
The main value of the gws-shared skill is reducing guesswork around command shape and flags. It gives you a stable way to express: what service/resource you want, what method you are calling, which flags apply globally, and how to choose between JSON, table, YAML, or CSV output.
How to Use gws-shared skill
Install and verify the skill
The repo notes that the gws binary must be on your $PATH; the skill itself is the shared reference, not the binary installer. For gws-shared install, first ensure gws is available, then read SKILL.md as the primary source of truth before using the command pattern in automation.
Read these files first
Start with skills/gws-shared/SKILL.md, then check the repository-level README or adjacent docs for the actual gws install options and environment setup. In this repo, the skill path is compact and there are no helper scripts or support folders, so the skill body is the important source: auth, flags, syntax, and security rules.
Turn a rough goal into a usable prompt
A strong gws-shared usage prompt should include the target service, resource, method, desired output format, and whether the action is read-only or potentially destructive. For example, instead of “manage users,” say: “Use gws-shared to list Workspace users in table format, avoid writes, and explain the safest command with --dry-run if available.”
Practical command shape to follow
The core syntax is gws <service> <resource> [sub-resource] <method> [flags]. Use method flags to narrow the call: --params for query arguments, --json for request bodies, --upload for file content, -o for binary output, and --page-all only when you expect multiple result pages. For gws-shared for Workflow Automation, specify whether the step is interactive, service-account based, or fully automated so the skill can choose the right auth and output behavior.
gws-shared skill FAQ
Is gws-shared only for advanced users?
No. The gws-shared skill is actually helpful for beginners because it removes ambiguity in authentication and command formatting. The main requirement is that you already have gws installed and know which Google Workspace object you want to act on.
When should I not use it?
Do not use gws-shared if you need a tutorial on the gws product from scratch or if your task is outside the CLI’s supported service/resource model. It is also not the right fit when you want a generic API description without command-ready syntax.
How is it different from a normal prompt?
A normal prompt may describe the goal, but gws-shared guide behavior gives you the shared operational rules: authentication options, safe flags, output modes, and pagination controls. That usually means fewer retries and less formatting drift in automation.
What are the main boundaries?
The skill supports read/write workflows only within the gws CLI conventions documented in SKILL.md. You still need to choose the right credentials, respect confirmation for write or delete actions, and avoid exposing secrets in output.
How to Improve gws-shared skill
Give the skill the missing context
The best inputs name the exact service, resource, method, and output target. For example: “Export Calendar events to CSV, use --page-all, limit to read-only calls, and keep the response safe for downstream parsing.” That is better than “summarize my calendar data” because it lets gws-shared choose the right flags and flow.
State safety and automation constraints up front
Because the repo emphasizes security rules, tell the skill whether the task may modify data, whether --dry-run should be used, and whether responses must be sanitized. This matters most for gws-shared for Workflow Automation, where a vague request can accidentally produce a write-capable command.
Iterate on the first command, not the whole workflow
If the first output is close but not exact, refine the input by changing one variable at a time: auth mode, format, pagination, or body parameters. The fastest path to better gws-shared usage is to correct the command shape before expanding scope, especially when working with binary output, uploads, or multi-page responses.