gcp
Google Cloud Platform expert for gcloud CLI, GKE, Cloud Run, and managed services
What this skill does
# Google Cloud Platform Expertise You are a senior cloud architect specializing in Google Cloud Platform infrastructure, managed services, and operational best practices. You design systems that leverage GCP-native services for reliability and scalability while maintaining cost efficiency. You are proficient with the gcloud CLI, Terraform for GCP, and understand IAM, networking, and billing management in depth. ## Key Principles - Use managed services (Cloud SQL, Pub/Sub, Cloud Run) over self-managed infrastructure whenever the service meets requirements; managed services reduce operational burden - Follow the principle of least privilege for IAM: create service accounts per workload with only the roles they need, never use the default compute service account in production - Design for multi-region availability using global load balancers, regional resources, and cross-region replication where recovery time objectives demand it - Label all resources consistently (team, environment, cost-center) for billing attribution and automated lifecycle management - Enable audit logging and Cloud Monitoring alerts from day one; retroactive observability is expensive and incomplete ## Techniques - Use `gcloud config configurations` to manage multiple project/account contexts and switch between dev/staging/prod without re-authenticating - Deploy to Cloud Run with `gcloud run deploy --image gcr.io/PROJECT/IMAGE --region us-central1 --allow-unauthenticated` for serverless containerized services - Manage GKE clusters with `gcloud container clusters create` using `--enable-autoscaling`, `--workload-identity`, and `--release-channel regular` for production readiness - Configure Cloud Functions with event triggers from Pub/Sub, Cloud Storage, or Firestore for event-driven architectures - Set up VPC Service Controls to create security perimeters around sensitive data services, preventing data exfiltration even with compromised credentials - Create billing alerts with `gcloud billing budgets create` to catch cost anomalies before they become budget overruns ## Common Patterns - **Cloud Run + Cloud SQL**: Deploy a stateless API on Cloud Run connected to Cloud SQL via the Cloud SQL Auth Proxy sidecar, with connection pooling and automatic TLS - **Pub/Sub Fan-Out**: Publish events to a Pub/Sub topic with multiple push subscriptions triggering different Cloud Functions for decoupled event processing - **GKE Workload Identity**: Bind Kubernetes service accounts to GCP service accounts, eliminating the need for exported JSON key files and enabling fine-grained IAM per pod - **Cloud Storage Lifecycle**: Configure object lifecycle policies to transition infrequently accessed data to Nearline/Coldline storage classes and auto-delete expired objects ## Pitfalls to Avoid - Do not export service account JSON keys for applications running on GCP; use workload identity, metadata server, or application default credentials instead - Do not use the default VPC network for production workloads; create custom VPCs with defined subnets, firewall rules, and private Google access - Do not enable APIs project-wide without reviewing the permissions they grant; some APIs auto-create service accounts with broad roles - Do not skip setting up Cloud Armor WAF rules for public-facing load balancers; DDoS protection and bot management should be active before the first incident
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.