Gcloud
Google Cloud SDK command-line tools. Use for GCP automation.From its SKILL.md
npx -y skills add G1Joshi/Agent-Skills --skill gcloudAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 12 stars12 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.6 KB, 363 tokens by cl100k_base, as published. Nobody here has run it
Google Cloud CLI (gcloud)
The gcloud CLI is part of the Google Cloud SDK. It manages authentication, local configuration, and developer workflows for GCP.
When to Use
- App Engine / Cloud Run:
gcloud app deployandgcloud run deployare the standard ways to ship code. - Kubernetes:
gcloud container clusters get-credentialsis essential for GKE access. - Auth:
gcloud auth loginsets up Application Default Credentials (ADC).
Quick Start
# Initialize
gcloud init
# Authenticate for local code (ADC)
gcloud auth application-default login
# Deploy to Cloud Run
gcloud run deploy my-service --source .
Core Concepts
Components
Installable modules. kubectl, beta, gke-gcloud-auth-plugin.
gcloud components install kubectl
Configurations
Use named configurations to switch between accounts/projects.
gcloud config configurations create dev
Alpha / Beta
GCP releases features rapidly. Many commands live under gcloud beta.
Best Practices (2025)
Do:
- Use ADC: For local development,
application-default loginis the correct way to auth your local Python/Node scripts. - Use
gcloud config set project: Don't pass--projectto every command. Set the context. - Scripting: Use
--format="json"andjqfor reliable automation.
Don't:
- Don't use Service Account Keys locally: They are risky. Use User Credentials (ADC) for local dev.
References
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.