cloud-operator-share-context
Shares Google Cloud operating context the user or their team already have — environments, projects, services and regions, product preferences, best practices, architecture guidance, runbooks — found in agent instruction files, local memory, skills and workflows, and the repository's GCP docs, with t…
Install / Use
npx skills add google/skills --skill cloud-operator-share-contextInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Our assessment of cloud-operator-share-context
cloud-operator-share-context scores 88/100 on our quality scale, 1485th of 2,790 Automation skills we index.
Its SKILL.md is 6.2 KB long, split into 5 sections and no code examples: a thorough specification that gives an agent plenty to work with.
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-share-context 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-share-context compared with similar skills
All 4 of these similar skills score higher than cloud-operator-share-context; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| cloud-operator-share-context (this skill)by google | 88 | 20.3k | 54d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 103.6k | 2d ago | MCP Server |
Frequently asked questions
- How do I install cloud-operator-share-context?
- Run
npx skills add google/skills --skill cloud-operator-share-context. The install tabs above show the steps for each supported agent. - Which AI agents does cloud-operator-share-context 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-share-context 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-share-context still maintained?
- The repository was last updated about 2 months ago, so cloud-operator-share-context is actively maintained.
Skill content
View source on GitHubname: cloud-operator-share-context metadata: version: "1.0.0" category: CloudInfrastructureAndServices description: >- Shares Google Cloud operating context the user or their team already have — environments, projects, services and regions, product preferences, best practices, architecture guidance, runbooks — found in agent instruction files, local memory, skills and workflows, and the repository's GCP docs, with the operator agent's memory after the user reviews the list. Use when the user runs this skill, accepts the cloud-operator or cloud-operator-setup skill's offer to share their existing Google Cloud context, or asks to share, import or save that context or a GCP fact for the operator agent. Don't use for ordinary GCP requests, which go to the cloud-operator skill.
Share existing Google Cloud context with the operator agent
Scan agent instruction files, local memory, skills and workflows, and the
repository's GCP docs for context the user or their team already have about
operating in Google Cloud, show it to the user, and copy what they approve into
the operator agent's memory. Use the cloud-operator skill's project,
agentId and secrets rules, including asking before using their default gcloud
project. Save the project once a call works.
Usage Attribution
MUST READ: Before executing any gcloud, REST API, or MCP command, you
MUST read and follow the instructions in
Usage Attribution.
One fact
If the user runs this skill with a fact, asks to save one GCP fact, or picks
their version after a conflict (Send, step 6), skip the review. Follow
Send, /reflect included, with the message "Please remember this about
how I work in Google Cloud for future sessions. It's current and replaces
anything you have that conflicts: {fact}". Then confirm in one line.
Existing Google Cloud context
-
Ask first, unless the user just agreed to an offer that named the sources. Name them: agent instruction files (
CLAUDE.md,AGENTS.md,GEMINI.md,.claude/rules), local memory, skills and workflows written for this user, and GCP docs in this repository. Say that the share takes only notes about how they operate in Google Cloud, takes no secrets, and shows the list before sending. If local memory notes a confirmed earlier share ("shared on"), say when and offer only what's new. Check local memory only for an earlier "shared on" note; read nothing else until they agree. If they say no, note "declined" (step 4) and stop. -
Collect in three groups, copying what the sources say (names, dates, reasons) rather than searching past transcripts:
- Facts and preferences: environments (test, staging, prod) and their projects, other projects of interest, the services they manage, regions, networks, where IaC and state live, naming, owners, product preferences, best practices, architecture guidance (standard patterns, approved services, network/landing-zone conventions) and other standing choices.
- What happened: incidents and fixes, migrations, decisions and failed attempts, each with its date and outcome.
- How things are done: deploys, rollbacks, failovers, incident response, quota or access requests, each as a short summary naming its resources, and where its runbook is.
Put any other note about how they operate in Google Cloud in the closest group. Leave out secrets, personal and non-GCP notes, and live state such as metrics or bills. Mark notes that apply to one repository only. When local sources disagree, keep the newer one (by its date) or ask; a conflict with what the operator already has is settled after the save (Send, step 6). If nothing qualifies, say so and stop.
-
Show the list, one line per note with its source, and ask: all, some or none?
-
Send the picks, then note in local memory "Cloud Operator context: shared on {date}", "declined on {date}" (no or none) or, if
/reflectdoesn't confirm, "not confirmed on {date}". Note nothing if a call failed. Only "shared on" and "declined on" stop the cloud-operator and cloud-operator-setup skills' offers.
Send
-
Use one new operator session for the whole share: no
contextIdat first, then each reply'scontext_id. -
Write in plain language and the user's voice, without tags or structured formats, which the safety filter can reject. Describe procedures as what the user does. Leave out empty groups, and above about 30 notes send one group per message:
These are notes about how I and my team operate in Google Cloud. Please remember them for future sessions and skip what you already have. If one conflicts with what you know, keep yours and tell me which, with your version and when you learned it. Reply with one line per note. Facts and preferences: - ... What happened: - ... How we do things: - ... -
If a call fails with a permission error while earlier calls worked, retry once in a new session with everything sent so far, in the same wording, so the operator skips notes it already saved. If that fails, tell the user the operator refused; mention IAM only if other calls fail too.
-
Send
/reflectalone, once, after the last message, without waiting on anything such as a conflict. The operator may save during the turn too;/reflectsaves everything now. -
If its reply doesn't say the conversation is being saved (for example, "nothing new to save"), the save isn't confirmed and memory may be off. Tell the user they can retry later by running this skill again.
-
Otherwise, report briefly what was shared, skipped or flagged. If the operator kept its own version of a note, show the user both versions, each with its source and date if known: theirs from the list, the operator's from its reply. Ask once, for all conflicts, which version is current. Where they pick theirs, send it with One fact, all in one message; it replaces the operator's version. Where they pick the operator's or don't answer, leave it. If the operator still keeps its own version after that, tell the user and stop.
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
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Scrapling
103.6k🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
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.
