gcloud
Google Cloud Platform CLI - manage GCP resources including Compute Engine, Cloud Run, GKE, Cloud Functions, Storage, BigQuery, and more.
What this skill does
# GCloud Skill Use the `gcloud` CLI to manage Google Cloud Platform resources and services. ## Authentication Check current auth: ```bash gcloud auth list ``` Login interactively: ```bash gcloud auth login ``` Login with service account: ```bash gcloud auth activate-service-account --key-file=key.json ``` Application default credentials: ```bash gcloud auth application-default login ``` ## Project & Configuration List projects: ```bash gcloud projects list ``` Set default project: ```bash gcloud config set project PROJECT_ID ``` Show current config: ```bash gcloud config list ``` Create named configuration: ```bash gcloud config configurations create my-config gcloud config configurations activate my-config ``` Set default region/zone: ```bash gcloud config set compute/region us-central1 gcloud config set compute/zone us-central1-a ``` ## Compute Engine (VMs) List instances: ```bash gcloud compute instances list ``` Create instance: ```bash gcloud compute instances create my-vm \ --zone=us-central1-a \ --machine-type=e2-medium \ --image-family=debian-12 \ --image-project=debian-cloud ``` SSH to instance: ```bash gcloud compute ssh my-vm --zone=us-central1-a ``` Stop/start instance: ```bash gcloud compute instances stop my-vm --zone=us-central1-a gcloud compute instances start my-vm --zone=us-central1-a ``` Delete instance: ```bash gcloud compute instances delete my-vm --zone=us-central1-a ``` ## Cloud Run List services: ```bash gcloud run services list ``` Deploy from source: ```bash gcloud run deploy my-service --source . --region=us-central1 ``` Deploy container: ```bash gcloud run deploy my-service \ --image=gcr.io/PROJECT/IMAGE \ --region=us-central1 \ --allow-unauthenticated ``` View logs: ```bash gcloud run services logs read my-service --region=us-central1 ``` Update traffic split: ```bash gcloud run services update-traffic my-service \ --to-revisions=LATEST=100 \ --region=us-central1 ``` ## Cloud Functions List functions: ```bash gcloud functions list ``` Deploy function (2nd gen): ```bash gcloud functions deploy my-function \ --gen2 \ --runtime=nodejs20 \ --region=us-central1 \ --trigger-http \ --entry-point=handler \ --source=. ``` View logs: ```bash gcloud functions logs read my-function --region=us-central1 ``` Delete function: ```bash gcloud functions delete my-function --region=us-central1 ``` ## Google Kubernetes Engine (GKE) List clusters: ```bash gcloud container clusters list ``` Get credentials for kubectl: ```bash gcloud container clusters get-credentials my-cluster \ --zone=us-central1-a ``` Create cluster: ```bash gcloud container clusters create my-cluster \ --zone=us-central1-a \ --num-nodes=3 ``` Resize node pool: ```bash gcloud container clusters resize my-cluster \ --node-pool=default-pool \ --num-nodes=5 \ --zone=us-central1-a ``` ## Cloud Storage List buckets: ```bash gcloud storage buckets list ``` Create bucket: ```bash gcloud storage buckets create gs://my-bucket --location=us-central1 ``` List objects: ```bash gcloud storage ls gs://my-bucket/ ``` Copy files: ```bash # Upload gcloud storage cp local-file.txt gs://my-bucket/ # Download gcloud storage cp gs://my-bucket/file.txt ./ # Recursive gcloud storage cp -r ./local-dir gs://my-bucket/ ``` Sync directory: ```bash gcloud storage rsync -r ./local-dir gs://my-bucket/remote-dir ``` ## Cloud SQL List instances: ```bash gcloud sql instances list ``` Create instance: ```bash gcloud sql instances create my-instance \ --database-version=POSTGRES_15 \ --tier=db-f1-micro \ --region=us-central1 ``` Connect via proxy: ```bash gcloud sql connect my-instance --user=postgres ``` Create database: ```bash gcloud sql databases create mydb --instance=my-instance ``` ## BigQuery List datasets: ```bash bq ls ``` Run query: ```bash bq query --use_legacy_sql=false 'SELECT * FROM dataset.table LIMIT 10' ``` Create dataset: ```bash bq mk --dataset my_dataset ``` Load data: ```bash bq load --source_format=CSV my_dataset.my_table gs://bucket/data.csv ``` ## Pub/Sub List topics: ```bash gcloud pubsub topics list ``` Create topic: ```bash gcloud pubsub topics create my-topic ``` Publish message: ```bash gcloud pubsub topics publish my-topic --message="Hello" ``` Create subscription: ```bash gcloud pubsub subscriptions create my-sub --topic=my-topic ``` Pull messages: ```bash gcloud pubsub subscriptions pull my-sub --auto-ack ``` ## Secret Manager List secrets: ```bash gcloud secrets list ``` Create secret: ```bash echo -n "my-secret-value" | gcloud secrets create my-secret --data-file=- ``` Access secret: ```bash gcloud secrets versions access latest --secret=my-secret ``` Add new version: ```bash echo -n "new-value" | gcloud secrets versions add my-secret --data-file=- ``` ## IAM List service accounts: ```bash gcloud iam service-accounts list ``` Create service account: ```bash gcloud iam service-accounts create my-sa \ --display-name="My Service Account" ``` Create key: ```bash gcloud iam service-accounts keys create key.json \ [email protected] ``` Add IAM binding: ```bash gcloud projects add-iam-policy-binding PROJECT_ID \ --member="serviceAccount:[email protected]" \ --role="roles/storage.admin" ``` ## Cloud Build Submit build: ```bash gcloud builds submit --tag gcr.io/PROJECT/IMAGE ``` List builds: ```bash gcloud builds list ``` View build logs: ```bash gcloud builds log BUILD_ID ``` ## Artifact Registry List repositories: ```bash gcloud artifacts repositories list ``` Configure Docker: ```bash gcloud auth configure-docker us-central1-docker.pkg.dev ``` ## Logging Read logs: ```bash gcloud logging read "resource.type=cloud_run_revision" --limit=50 ``` Tail logs: ```bash gcloud logging tail "resource.type=gce_instance" ``` ## App Engine Deploy app: ```bash gcloud app deploy ``` View logs: ```bash gcloud app logs tail ``` Browse app: ```bash gcloud app browse ``` ## Useful Flags Format as JSON: ```bash gcloud compute instances list --format=json ``` Format as table with specific columns: ```bash gcloud compute instances list --format="table(name,zone,status)" ``` Filter results: ```bash gcloud compute instances list --filter="status=RUNNING" ``` Quiet mode (no prompts): ```bash gcloud compute instances delete my-vm --quiet ``` ## Cheat Sheet Quick reference: ```bash gcloud cheat-sheet ``` Interactive shell: ```bash gcloud interactive ```
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.