How to use the Install Google Workspace and GCP CLIs agent skill

What is an agent skill, and what does this one do?

An agent skill is a folder containing a SKILL.md file that gives an AI agent instructions for one kind of task. The agent loads the instructions when a request matches them.

This skill covers four tools: gws for Google Workspace (Drive, Gmail, Sheets, Calendar, Chat), gcloud for Google Cloud, agents-cli for calling remotely deployed agents, and mcp-cli for using tools exposed by MCP servers. The tools are independent, so the skill installs only the one the task needs. It is a menu, not a fixed sequence.

• Checks whether a tool is already present with command -v before installing anything.
• Installs Node and npm under ~/.local when gws needs them.
• Stores OAuth clients, tokens and config in /workspace/lha/config so logins can survive a runtime-image upgrade.
• Probes for an existing Connect Workspace token before asking you to set up new credentials.
• Hands off to other skills (such as google-workspace) for actual usage.

Install the skill in Claude

Download the ZIP from this page and unzip it. For a personal setup, place the bootstrap-google-tools folder inside ~/.claude/skills/. For a single project, place it inside that project's .claude/skills/ folder.

Alternatively, upload the ZIP in the Claude apps under Settings → Capabilities → Skills.

• Personal: ~/.claude/skills/bootstrap-google-tools/
• Project: .claude/skills/bootstrap-google-tools/ inside your project

Trigger the skill with natural requests

The skill loads when a request involves Google Workspace, Google Cloud or MCP tools and the command is missing, or when you ask the agent to prepare for that work. The source names the trigger phrase "command not found" and the situation of preparing before GCP, Workspace or MCP work.

Plain requests that fit the description include asking the agent to set up gws so it can read a Drive folder, or asking it to install gcloud before a Cloud task.

• "gws: command not found. Set up the Google Workspace CLI so you can list my Drive files."
• "Install gcloud and log me in before we start the Cloud Run work."
• "Get mcp-cli installed so you can call the tools on this MCP server."

What the skill needs before it runs

The skill is written for a Debian x86_64 sandbox that has curl and tar but no xz. It downloads Node.js LTS from nodejs.org and packages from the npm registry, so network access to those hosts is required.

For Google Workspace you need one of three credential sources: a Google OAuth Desktop-app client, a service account key, or a Connect Workspace token from the web UI. Interactive OAuth login needs a person to paste a redirect URL back to the agent.

• Debian x86_64 sandbox with curl and tar (no xz)
• Node.js LTS, installed by the skill
• npm registry and nodejs.org access
• One Google credential source: Desktop-app OAuth client, service account key, or Connect Workspace token

Safety notes: scripts and network access

This skill runs scripts and uses the network. It downloads software, runs npm install -g, and can create OAuth clients or handle tokens. Review the SKILL.md before you install it if your environment is sensitive.

Credentials are stored in a folder under /workspace. Anyone with access to that folder can use the saved logins, so do not use this skill where a shared folder would expose them.

• Do not use it on a local machine where these tools already work. It assumes the /workspace and ~/.local layout.
• Do not use it for unattended jobs unless you have a service account, because interactive login requires a person.
• A Connect Workspace token only carries the surfaces and access level you chose and lasts about an hour without refresh.

Tips for smoother results

Ask for one tool at a time. The skill is designed to install only what the task needs, and a smaller request is easier to verify.

If a Google call returns a 403 or scope error, the token probably lacks the surface or read-write access you need. Reconnect with more surfaces rather than treating it as a missing token. Use a real read such as a Gmail list call to check, because gws auth status can report none even when reads succeed.

After gws is working, the source suggests installing Google's official gws skills from the googleworkspace/cli repository, such as gws-gmail or gws-drive.

• Use the google-workspace skill for auth details and command shapes.
• Run command -v gws first if you are unsure what is already installed.