gcloud
Google Cloud CLI for managing GCP resources. Use when the user needs to work with Compute Engine, Cloud Storage, Cloud Functions, IAM, GKE, and other Google Cloud services from the terminal.
What this skill does
# Google Cloud CLI The `gcloud` CLI manages GCP resources, configurations, and deployments from the terminal. ## Setup ```bash # Install gcloud CLI curl https://sdk.cloud.google.com | bash exec -l $SHELL # Initialize and authenticate gcloud init gcloud auth login gcloud auth application-default login # Set project and region gcloud config set project my-project-id gcloud config set compute/region us-central1 gcloud config set compute/zone us-central1-a # Named configurations for multiple projects gcloud config configurations create production gcloud config configurations activate production ``` ## Compute Engine ```bash # Create a VM instance gcloud compute instances create web-server \ --machine-type=e2-medium \ --image-family=ubuntu-2204-lts \ --image-project=ubuntu-os-cloud \ --boot-disk-size=30GB \ --boot-disk-type=pd-ssd \ --subnet=my-subnet \ --tags=http-server,https-server \ [email protected] # List instances gcloud compute instances list \ --filter="status=RUNNING AND labels.env=production" \ --format="table(name,zone,machineType.basename(),networkInterfaces[0].accessConfigs[0].natIP)" # SSH into instance gcloud compute ssh web-server --zone=us-central1-a # Stop/start/delete gcloud compute instances stop web-server --zone=us-central1-a gcloud compute instances start web-server --zone=us-central1-a gcloud compute instances delete web-server --zone=us-central1-a # Firewall rules gcloud compute firewall-rules create allow-http \ --network=default --allow=tcp:80,tcp:443 \ --target-tags=http-server --source-ranges=0.0.0.0/0 ``` ## Cloud Storage ```bash # Bucket operations gcloud storage buckets create gs://my-bucket --location=us-central1 gcloud storage ls gs://my-bucket/ gcloud storage cp file.txt gs://my-bucket/path/ gcloud storage rsync ./local-dir gs://my-bucket/remote/ --delete-unmatched-destination-objects # Set lifecycle rules gcloud storage buckets update gs://my-bucket \ --lifecycle-file=lifecycle.json # Signed URLs gcloud storage sign-url gs://my-bucket/file.pdf --duration=1h ``` ## Cloud Functions ```bash # Deploy a Cloud Function (2nd gen) gcloud functions deploy my-function \ --gen2 \ --runtime=python312 \ --region=us-central1 \ --source=. \ --entry-point=handler \ --trigger-http \ --allow-unauthenticated \ --memory=256MB \ --timeout=60s \ --set-env-vars="DB_HOST=10.0.0.5,ENV=production" # Invoke and view logs gcloud functions call my-function --data='{"key":"value"}' gcloud functions logs read my-function --region=us-central1 --limit=50 # List functions gcloud functions list --format="table(name,status,runtime)" ``` ## IAM ```bash # Service accounts gcloud iam service-accounts create app-sa \ --display-name="Application Service Account" gcloud iam service-accounts keys create key.json \ [email protected] # Role bindings gcloud projects add-iam-policy-binding my-project \ --member="serviceAccount:[email protected]" \ --role="roles/storage.objectViewer" # View IAM policy gcloud projects get-iam-policy my-project \ --format="table(bindings.role,bindings.members)" # Impersonate service account gcloud auth print-access-token --impersonate-service-account=app-sa@my-project.iam.gserviceaccount.com ``` ## GKE ```bash # Create GKE cluster gcloud container clusters create my-cluster \ --num-nodes=3 \ --machine-type=e2-standard-4 \ --region=us-central1 \ --enable-autoscaling --min-nodes=1 --max-nodes=10 # Get credentials for kubectl gcloud container clusters get-credentials my-cluster --region=us-central1 # Resize node pool gcloud container clusters resize my-cluster --num-nodes=5 --region=us-central1 ``` ## Useful Patterns ```bash # Format output for scripting gcloud compute instances list --format="value(name)" | while read name; do echo "Processing $name" done # Describe any resource as JSON gcloud compute instances describe web-server --zone=us-central1-a --format=json # Billing and cost gcloud billing accounts list gcloud billing projects describe my-project # Cloud SQL gcloud sql instances create my-db --database-version=POSTGRES_15 \ --tier=db-custom-2-8192 --region=us-central1 gcloud sql connect my-db --user=postgres # Pub/Sub gcloud pubsub topics create my-topic gcloud pubsub subscriptions create my-sub --topic=my-topic ```
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.