cloud-operator-setup
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
Install / Use
npx skills add google/skills --skill cloud-operator-setupInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
OperationsSupported Platforms
Our assessment of cloud-operator-setup
cloud-operator-setup scores 82/100 on our quality scale, 622nd of 745 Operations skills we index.
Its SKILL.md is 3.3 KB long, split into 3 sections and no code examples: a solid amount of guidance for an agent.
With 20,340 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so cloud-operator-setup is actively maintained.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit ā read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-15. Automated pattern scan on 2026-11-15. It catches known dangerous patterns, not every risk ā read a skill before letting an agent act on it.
cloud-operator-setup compared with similar skills
All 4 of these similar skills score higher than cloud-operator-setup; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| cloud-operator-setup (this skill)by google | 82 | 20.3k | 54d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
| CowAgentby zhayujie | 100 | 48.0k | today | CLAUDE.md |
Frequently asked questions
- How do I install cloud-operator-setup?
- Run
npx skills add google/skills --skill cloud-operator-setup. The install tabs above show the steps for each supported agent. - Which AI agents does cloud-operator-setup work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is cloud-operator-setup safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is cloud-operator-setup still maintained?
- The repository was last updated about 2 months ago, so cloud-operator-setup is actively maintained.
Skill content
View source on GitHubname: 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.
Steps
- Choose the project: ask which Google Cloud project their operator agent
is in, or will be in (unless already named). Suggest their default
gcloudproject or the project in local memory only as an option; don't use either without asking. - Check or create the agent:
- Unless the user said they have no agent in
{project_id}, check first: callask_cloud_operatorwithprojects/{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).
- Unless the user said they have no agent in
- Save and offer to share context: once the check call works, save
{project_id}in local memory (andagentIdif not their own) and tell the user the operator works, with{project_id}and the agent. In that same reply, if thecloud-operator-share-contextskill 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.
- Yes: run
Related Skills
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu ā one CLI, zero API fees.
ruflo
81.9kš The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
CowAgent
48.0kOpen-source personal AI assistant & Agent Harness. Plans tasks, runs tools and skills, self-evolves with memory and knowledge. Multi-agent, multi-model, multi-channel. Lightweight, extensible, one-line install.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit ā see the Safety scan above for what the skill file itself contains.
