gcloud
Skill4 starsChanged 9 months agoMITView on GitHub
Google Cloud Platform CLI (gcloud, gcloud storage, bq). Use when: managing GCP resources, deploying to Cloud Run/Cloud Functions/GKE/App Engine, working with Cloud Storage, BigQuery, IAM, Compute Engine, Cloud SQL, Pub/Sub, Secret Manager, Artifact Registry, Cloud Build, Cloud Scheduler, Cloud Tasks, Vertex AI, VPC/networking, DNS, logging/monitoring, or any GCP service. Also covers: authentication, project/config management, CI/CD integration, serverless deployments, container registry, docker push to GCP, managing secrets, Workload Identity Federation, and infrastructure automation.
13 other projects use a version of this.
Adopted by
Most recently taken up by
- oivanfelipe/claude-skillstheir own version, first seen Nov 8, 2026
- fmind/dottheir own version, first seen Nov 8, 2026
- fmind/dotfilestheir own version, first seen Nov 8, 2026
- paradigmxyz/centaurtheir own version, first seen Nov 1, 2026
- iboumedien/claude-skillstheir own version, first seen Oct 20, 2026
- olaitanojo/skillstheir own version, first seen Oct 17, 2026
Used with
Projects with it also use aws.
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.
VercelSkillaws
Emulated AWS cloud services (S3, SQS, Cognito, IAM, STS) for local development and testing. Use when the user needs to interact with AWS API endpoints locally, test S3 bucket and object operations, emulate SQS queues and messages, test Cognito sign-up, sign-in, JWTs, or Identity Pools, manage IAM users/roles/access keys, test STS assume role, or work without hitting real AWS APIs. Triggers include "AWS emulator", "emulate AWS", "mock S3", "local SQS", "test IAM", "emulate S3", "AWS locally", "STS assume role", or any task requiring local AWS service emulation.
Also in 4 projects that use this
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- google/skills★ 24ksame name
- paradigmxyz/centaur★ 1.4ksame name
- Dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations★ 73same name
- G1Joshi/Agent-Skills★ 15same name
- rittmananalytics/wire-plugin★ 14same name
- fmind/dot★ 13same name
- fmind/dotfiles★ 13same name
- jholhewres/devclaw-skills★ 4same name
- Adhamxon/claude-code-skills★ 2same name
- ai-ecoverse/skills★ 1same name
3 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 repository7 other files it gives its agents.
- azcliSkill
- pm2Skill
- pre-releaseSkill
- repo-hygieneSkill
- sheet-modelSkill
- vhsSkill
- web-searchSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
If installed via scoop, gcloud components install may not work — use scoop to manage
- Distinctive: line 86
Before working with any GCP service:
“Common” is measured: kept by at least 6 in 10 of the 12 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
gcloud — Google Cloud Platform CLI
Command-line interface for managing Google Cloud resources.
Covers gcloud, gcloud storage (replaces gsutil), and bq (BigQuery).
Platform Notes (Windows + Git Bash)
- Install:
scoop install gcloud(preferred) orGoogleCloudSDKInstaller.exe - If installed via scoop,
gcloud components installmay not work — use scoop to manage - Config:
%APPDATA%/gcloud/(PowerShell) or~/.config/gcloud/(Git Bash) - Service account keys: store in
$TEMPor project.secrets/, never commit - Python: gcloud requires Python; scoop install handles this automatically
⚠️ Path Translation Gotcha
Git Bash auto-translates /-prefixed args, breaking some gcloud commands:
# FIX — disable MSYS path conversion:
export MSYS_NO_PATHCONV=1
# Or per-command:
MSYS_NO_PATHCONV=1 gcloud projects add-iam-policy-binding my-project ...⚠️ Cost: Commands that create resources (instances, clusters, databases) incur GCP charges. Always confirm project and region before creating.
Agent Safety Model
Operations classified by risk. Follow this model for all gcloud commands.
| Level | Gate | Examples |
| READ | Proceed autonomously | list, describe, get, logs read, config list, gcloud storage ls |
| WRITE | Confirm with user; note cost if billable | create, deploy, update, enable, gcloud storage cp (upload) |
| DESTRUCTIVE | Always confirm; show what's affected | delete, rm, gsutil rm -r, bq rm -r, rsync -d, IAM removal |
| EXPENSIVE | Confirm + state approximate cost | GKE clusters ( |
| SECURITY | Confirm + explain impact | --allow-unauthenticated, firewall rules, IAM owner/editor grants |
| FORBIDDEN | Refuse; escalate to human | gcloud iam service-accounts keys create, gcloud projects delete, passwords in CLI args |
Rules:
- Never combine
--quietwith destructive operations — it suppresses the only safety gate - Never put passwords/secrets as command-line arguments — visible in process list & shell history
- Always use
--format=jsonfor machine-parseable output (agents can't reliably parse tables) - When in doubt, treat as DESTRUCTIVE
Command Structure
gcloud [RELEASE_LEVEL] COMPONENT ENTITY OPERATION [ARGS] [FLAGS]Key global flags: --project, --format, --filter, --limit, --quiet, --verbosity, --async
Service Reference
| Service | File | Key Commands |
| Auth & Config | auth.md | Login, ADC, impersonation, config profiles |
| IAM & Projects | iam.md | Projects, APIs, service accounts, Secret Manager |
| Compute & Networking | compute.md | VMs, SSH, firewall, VPC, DNS, static IPs |
| Serverless | serverless.md | Cloud Run, Functions, App Engine, Scheduler, Tasks |
| Storage & Artifacts | storage.md | gcloud storage, Artifact Registry |
| Data | data.md | Cloud SQL, BigQuery (bq), Pub/Sub |
| Automation & CI/CD | automation.md | Scripting, output formats, filtering, GitHub Actions, operations |
Read the per-service file for full command reference.
Pre-Flight Checks
Before working with any GCP service:
# 1. Correct project?
gcloud config get-value project
# 2. Default region set?
gcloud config get-value compute/region
# 3. Required API enabled? (most APIs are disabled by default)
gcloud services list --filter="name:run.googleapis.com" --format="value(name)" | grep -q run || \
gcloud services enable run.googleapis.com
# 4. Billing enabled?
gcloud billing projects describe $(gcloud config get-value project) --format="value(billingEnabled)"If you hit PERMISSION_DENIED: ... API has not been enabled, enable the API
mentioned in the error and retry.
Troubleshooting
| Problem | Diagnosis | Fix |
| Auth failure | gcloud auth list | gcloud auth login or check key file |
| Permission denied | Check IAM (see iam.md) | Grant correct role |
| API not enabled | Error message says which API | gcloud services enable API_NAME |
| Quota exceeded | gcloud compute project-info describe | Request increase in Console |
| Wrong project | gcloud config get-value project | gcloud config set project X |
| Wrong region | gcloud config get-value compute/region | Set correct region; related resources must match |
| Config confusion | gcloud config configurations list | Check active config, override with --project |
| Slow commands | Large result set | Use --filter, --limit, --format=value |
# Debug mode
gcloud compute instances list --verbosity=debug
# Full environment info
gcloud infoQuick Reference
| Task | Command |
| Login | gcloud auth login |
| Set project | gcloud config set project PROJECT_ID |
| Current project | gcloud config get-value project |
| Enable API | gcloud services enable API.googleapis.com |
| List anything | gcloud COMPONENT list --format=json |
| Describe anything | gcloud COMPONENT describe NAME --format=json |
| JSON output | --format=json |
| Single value | --format="value(field)" |
| Filter | --filter="field=value" |
| Quiet ⚠️ | --quiet — suppresses ALL prompts including delete confirmations |
| Help | gcloud COMPONENT --help |
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.