Skip to main content
skill CX Codex official · Google

cloud-operator-setup — Claude Code skill: setup guide

The cloud-operator-setup Claude Code skill sets up an operator agent in a Google Cloud project. Run it to create your operator or start its setup.

Apache-2.0 ★ 24,522 updated 2026-10-23

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add google/skills --skill cloud-operator-setup -a claude-code
Open on GitHub

What cloud-operator-setup does

The skill selects a Google Cloud project, checks whether its operator agent is ready, and guides the user through creating one if needed. Once the check succeeds, it saves the project in local memory.

It needs the autocloud MCP server and its ask_cloud_operator tool. If the server is disconnected, the skill stops and guides the user through gcloud auth application-default login; the server must then be reconnected. Read the usage attribution instructions before running any gcloud, REST API, or MCP command.

After setup, the skill can ask to share existing Google Cloud context with the operator’s memory. It waits for consent before reading instruction files, local memory, skills, workflows, or GCP documents in the repository, and presents the collected list first.

What it helps with

  • choose a Google Cloud project for the operator
  • check whether an operator agent exists in a project
  • create an agent that has not been initialized
  • save the project and offer to share existing cloud context

Example prompts for the agent

  • Set up an operator for my Google Cloud project.
  • Create my operator agent in the my-project project.
  • Check the operator in my-project and save that project.

How to install cloud-operator-setup

1Skills CLI (Vercel)

npx skills add google/skills --skill cloud-operator-setup -a claude-code

2Manually: put the files in place

~/.claude/skills/cloud-operator-setup/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/cloud-operator-setup/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about cloud-operator-setup

How do I install cloud-operator-setup in Claude Code?

Run npx skills add google/skills --skill cloud-operator-setup -a claude-code. The skill is installed at ~/.claude/skills/cloud-operator-setup/SKILL.md.

What does cloud-operator-setup do?

It selects a Google Cloud project, checks for an operator agent, and guides the setup if the agent needs to be created. It saves the project after the check succeeds and can offer to share existing cloud context.

What does cloud-operator-setup need to run?

It requires the autocloud MCP server with the ask_cloud_operator tool and a Google Cloud project. If the server is disconnected, the skill guides the user through gcloud auth application-default login and waits for the server to reconnect.

Source text

SKILL.md · Apache-2.0
---
name: cloud-operator-setup
metadata:
  version: "1.0.0"
  category: CloudInfrastructureAndServices
description: >-
  Sets up the operator agent in a Google Cloud project via the autocloud MCP
  server: picks the operator project, creates or checks the user's operator
  agent, saves the project, and offers to share the user's existing Google
  Cloud operating context with the operator agent's memory. Use when the user
  runs this skill, asks to set up the operator or create their operator agent,
  or chooses setup when the cloud-operator skill asks. Don't use for ordinary
  GCP requests or installing gcloud.
---

# Set up the operator agent

Walk the user through setting up the operator agent one step at a time. Follow
the `cloud-operator` skill's `agentId` and troubleshooting rules if installed.
If `ask_cloud_operator` (on the `autocloud` MCP server) isn't available, tell
the user it isn't connected, help them sign in with Application Default
Credentials (`gcloud auth application-default login`), and stop until they
reconnect.

## Usage Attribution

**MUST READ**: Before executing any `gcloud`, REST API, or MCP command, you
MUST read and follow the instructions in
[Usage Attribution](references/attribution.md).

## Steps

1. **Choose the project:** ask which Google Cloud project their operator agent
   is in, or will be in (unless already named). Suggest their default `gcloud`
   project or the project in local memory only as an option; don't use either
   without asking.
2. **Check or create the agent:**
   - Unless the user said they have no agent in `{project_id}`, check first:
     call `ask_cloud_operator` with `projects/{project_id}` and "In one line,
     what can you help me with in this project? Don't create anything." Tell
     the user first that it can take 1–3 minutes.
   - If it fails with "personal operator agent … has not been initialized yet"
     (or they said they have none), walk them through creating it one step at a
     time and wait for confirmation: open
     `https://console.cloud.google.com/autocloud/home?project={project_id}`,
     click **Create operator agent**, then click **Get started** when it says
     the agent is ready. Once they confirm, run the check call above (waiting
     about a minute and retrying up to 3 times if the new agent isn't ready
     yet).
3. **Save and offer to share context:** once the check call works, save
   `{project_id}` in local memory (and `agentId` if not their own) and tell the
   user the operator works, with `{project_id}` and the agent. In that same
   reply, if the `cloud-operator-share-context` skill is available and local
   memory has no "Cloud Operator context: shared on" or "declined on" note, ask
   in one line whether to scan agent instruction files, local memory, skills
   and workflows, and the repository's GCP docs for context they or their team
   already have about operating in Google Cloud (environments, projects,
   product preferences, best practices, architecture guidance, runbooks) and
   share it with the operator agent's memory — noting they'll see the list
   first. Read nothing else until they agree.
   - **Yes:** run `cloud-operator-share-context` (from its collection step).
   - **No:** note "Cloud Operator context: declined on {date}" in local memory.
   - **No answer:** note nothing.
   Then return to any request that was waiting when setup started.

© google · Apache-2.0 · google/skills

Similar skills

All skills for Cloud: AWS, Azure, GCP →
huawei-cloud-msot-msopprof-operator-profiler huaweicloud huawei-cloud-msot-msopprof-operator-profiler collects operator-level execution data on Ascend NPUs using msopprof in device or simulator mode and generates analysis reports. CX Codex +1 162installs huawei-cloud-ascendc-operator-performance-optim huaweicloud The huawei-cloud-ascendc-operator-performance-optim skill guides AscendC operator development and tuning for Ascend NPUs, from profiling bottlenecks to checking results. Use it when an operator is missing or slows a workload. CX Codex +1 219installs cloud-architect https://github.com/Jeffallan A skill for designing cloud architectures on AWS, Azure and GCP: redundant topology, migration plan, cost model and a disaster recovery strategy. CX Codex +1 5,100installs google-cloud-data-engineering-hub reason-machines google-cloud-data-engineering-hub — a skill that hands your coding agent a reference set of working GCP data projects: BigQuery, Dataflow, Beam, Composer, Pub/Sub, Dataproc, Vertex AI. CX Codex +1 1,100installs gcp-cloud-architect Alireza Rezvani gcp-cloud-architect — a Claude Code skill that designs Google Cloud architectures and generates infrastructure as code from them. Kick it off for Cloud Run or GKE deployments, BigQuery pipelines, cost estimates, or a move to GCP. CX Codex +1 717installs gcp-cloud-run aj-geddes gcp-cloud-run guides container deployments to Google Cloud Run with gcloud CLI and Terraform. Useful when releasing stateless HTTP backends. CX Codex +1 545installs

From the same set203

The whole set →
compute-vm-creation The compute-vm-creation skill automates planning and provisioning of standalone Google Compute Engine VMs. It assists in configuring hardware, regional placement, and network settings via CLI or MCP tools. CX Codex +1 ★ 24,522repo stars compute-spot-capacity-advice The compute-spot-capacity-advice Claude Code skill assesses Google Compute Engine Spot VM capacity and placement. It runs during batch planning, when comparing machine families or regions. CX Codex +1 ★ 24,522repo stars cloud-operator Delegates Google Cloud infrastructure operations to Cloud Operator via the autocloud MCP server. Triggers before modifying local Terraform or Kubernetes configs. CX Codex +1 ★ 24,522repo stars cloud-operator-share-context The cloud-operator-share-context Claude Code skill transfers existing Google Cloud operating notes to an operator agent’s memory. It runs when someone asks to import or save GCP context. CX Codex +1 ★ 24,522repo stars cloud-monitoring-alert-configuration The cloud-monitoring-alert-configuration Claude Code skill configures Cloud Monitoring alert policies with Terraform and PromQL. It activates for creating, reviewing, migrating, or deduplicating those policies. CX Codex +1 ★ 24,522repo stars cloud-armor-crs-rule-upgrader The cloud-armor-crs-rule-upgrader Claude Code skill upgrades Google Cloud Armor WAF rules from OWASP CRS 3.0 or 3.3 to CRS 4.22. It runs for policy audits and rule-set migrations. CX Codex +1 ★ 24,522repo stars bigquery-migration-validator The bigquery-migration-validator Claude Code skill checks whether BigQuery tables match their source. It runs during validation setup, execution, and investigation of migration mismatches. CX Codex +1 ★ 24,522repo stars bigquery-migration-metadata-extractor bigquery-migration-metadata-extractor — a skill for Claude Code runs catalog metadata and query log dumps from external warehouses into Cloud Storage. It triggers extraction jobs and parses summary statistics. CX Codex +1 ★ 24,522repo stars

Project sponsors

Companies that keep this analytics open