Menu
Guides an operator through a reviewed Google Workspace CLI installation and OAuth setup.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Creates a trusted local MCP extension with bounded tools and explicit enablement.
Creates a focused local Tars skill for a repeatable workflow.
Audits, enables, disables, and refreshes trusted local MCP extensions.
Operates and maintains a Tars installation through supported CLI commands.
| name | gws-setup |
| description | Guides an operator through a reviewed Google Workspace CLI installation and OAuth setup. |
Use this skill only when the user asks to connect Google Workspace through the external gws CLI.
This is not a built-in Tars integration.
gws --version and gws --help to confirm the installed command and current syntax.Do not guess current download URLs or authentication commands; the external project may change.
Follow the CLI's current official OAuth setup flow using a dedicated Google Cloud project and a Desktop OAuth client. Enable only the Workspace APIs required by the user's workflow and choose the smallest OAuth scopes that work.
Never paste a client secret, access token, or refresh token into chat, Tars memory, a skill file, or the repository. Store and revoke credentials using the external CLI's documented credential store.
If the installed version supports skill generation, direct output to ~/.tars/skills/ and review
every generated SKILL.md before use. Remove recipes that request broader scopes or actions than the
user needs, then run:
tars memory sync
Generated skills are instructions; they do not create a sandbox or independently authorize Google Workspace changes.