agentleFS
GoogleKnown publishergoogle/skills/skills/cloud/cloud-operator-setup/SKILL.md

cloud-operator-setup

Skill24k starsChanged 48 days agoApache-2.0View on GitHub

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.

Trending

Less talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 6 mentionsMay 2026: 2 mentionsJun 2026: 11 mentionsJul 2026: 0 mentionsAug 2026: 3 mentionsSep 2026: 5 mentionsOct 2026: 5 mentionsNov 2026: 3 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the google/skills repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about google/skills

The biggest 5 of 35 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 35

Talked about on Bluesky, GitHub, the web and Hacker News (35 times).

On Bluesky · 15

10 more on Bluesky

On GitHub · 14

9 more on GitHub

On the web · 4

On Hacker News · 2

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 1 is distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    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 …

    line 20
  2. Very specific:

    MUST READ: Before executing any gcloud, REST API, or MCP command, you MUST read and follow the instructions in Usage Attribution.

    line 27
  3. Distinctive:

    MUST read and follow the instructions in Usage Attribution.

    line 28
  4. Very specific:

    Choose the project: ask which Google Cloud project their operator agent is in, or will be in (unless already named).

    line 33
  5. Very specific:

    If it fails with "personal operator agent … has not been initialized yet" (or they said they have none), walk them through creating it one …

    line 42
  6. Very specific:

    Yes: run cloud-operator-share-context (from its collection step).

    line 61

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.