Google CloudKnown publisherGoogleCloudPlatform/gemini-cloud-assist-mcp/plugins/cloud-operator/skills/setup/SKILL.mdsetup
Skill72 starsChanged 2 days agoApache-2.0View on GitHub
Sets up Cloud Operator: 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's memory. Use when the user runs /cloud-operator:setup, asks to set up Cloud Operator or create their operator agent, or chooses setup when the cloud-operator skill asks. Not for ordinary GCP requests or installing gcloud.
191 other projects use a version of this.
Adopted by
Most recently taken up by
- finolabs/vibecodetheir own version, first seen Nov 15, 2026
- quickchatai/quickreviewtheir own version, first seen Nov 15, 2026
- tomw1808/flash-agentstheir own version, first seen Nov 15, 2026
- felipeam86/pipe-skillstheir own version, first seen Nov 15, 2026
- oss-invisible/playwright_mcptheir own version, first seen Nov 15, 2026
- facebookresearch/autoform-bottheir own version, first seen Nov 12, 2026
Used with
Projects with it also use add-voice-transcription, add-discord and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
juancruzmunozalbeloSkilladd-voice-transcription
Add voice message transcription to NanoClaw using OpenAI's Whisper API. Automatically transcribes WhatsApp voice notes so the agent can read and respond to them.
Also in 5 projects that use this
MicrosoftSkilladd-discord
Add Discord bot channel integration via Chat SDK.
Also in 11 projects that use this
- MicrosoftSkill
add-slack
Add Slack channel integration via Chat SDK.
Also in 11 projects that use this
- juancruzmunozalbeloSkill
add-telegram-swarm
Add Agent Swarm (Teams) support to Telegram. Each subagent gets its own bot identity in the group. Requires Telegram channel to be set up first (use /add-telegram). Triggers on "agent swarm", "agent teams telegram", "telegram swarm", "bot pool".
Also in 7 projects that use this
- +8 more from microsoft
Other versions191 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 191
- anthropics/knowledge-work-plugins★ 36ksame name
- garrytan/gbrain★ 32ksame name
- gavrielc/nanoclaw★ 31ksame name
- nanocoai/nanoclaw★ 31ksame name
- qwibitai/nanoclaw★ 31ksame name
- Q00/ouroboros★ 6.3ksame name
- pytorch/executorch★ 5.2ksame name
- aws/agent-toolkit-for-aws★ 3.5ksame name
- agenticnotetaking/arscontexta★ 3.5ksame name
- spotify/portal-ai-plugins★ 2.8ksame name
181 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
- cloud-operatorSkill
- share-contextSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 170 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Choose the project: ask which Google Cloud project their operator agent is in, or will be in (unless already named).
- Very specific: line 27
If it fails with "personal operator agent … has not been initialized yet" (or they said they have none), walk them through creating it one …
- Very specific: line 45
Yes: run the share-context skill (from its collection step).
“Common” is measured: kept by at least 6 in 10 of the 170 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Set up Cloud Operator
Walk the user through setting up Cloud Operator one step at a time. Follow the
cloud-operator skill's connection, agentId, usage attribution, and
troubleshooting rules.
- 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 Cloud Operator works, with{project_id}and the agent. In that same reply, unless local memory has a "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's memory — noting they'll see the list first. Read nothing else until they agree.- Yes: run the
share-contextskill (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 the
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.