gcp-cloud-run
Deploy containerized applications on Google Cloud Run with automatic scaling, traffic management, and service mesh integration. Use for container-based serverless computing.
What this skill does
# GCP Cloud Run ## Table of Contents - [Overview](#overview) - [When to Use](#when-to-use) - [Quick Start](#quick-start) - [Reference Guides](#reference-guides) - [Best Practices](#best-practices) ## Overview Google Cloud Run enables deployment of containerized applications at scale without managing infrastructure. Run stateless HTTP containers with automatic scaling from zero to thousands of instances, paying only for compute time consumed. ## When to Use - Microservices and APIs - Web applications and backends - Batch processing jobs - Long-running background workers - CI/CD pipeline integration - Data processing pipelines - WebSocket applications - Multi-language services ## Quick Start Minimal working example: ```bash # Build container image gcloud builds submit --tag gcr.io/MY_PROJECT_ID/my-app:latest # Deploy to Cloud Run gcloud run deploy my-app \ --image gcr.io/MY_PROJECT_ID/my-app:latest \ --platform managed \ --region us-central1 \ --memory 512Mi \ --cpu 1 \ --timeout 3600 \ --max-instances 100 \ --min-instances 1 \ --no-allow-unauthenticated \ --set-env-vars NODE_ENV=production,DATABASE_URL=postgresql://... # Allow public access gcloud run services add-iam-policy-binding my-app \ --platform managed \ --region us-central1 \ --member=allUsers \ --role=roles/run.invoker # Get service URL gcloud run services describe my-app \ // ... (see reference guides for full implementation) ``` ## Reference Guides Detailed implementations in the `references/` directory: | Guide | Contents | |---|---| | [Cloud Run Deployment with gcloud CLI](references/cloud-run-deployment-with-gcloud-cli.md) | Cloud Run Deployment with gcloud CLI | | [Containerized Application (Node.js)](references/containerized-application-nodejs.md) | Containerized Application (Node.js) | | [Terraform Cloud Run Configuration](references/terraform-cloud-run-configuration.md) | Terraform Cloud Run Configuration | | [Docker Build and Push](references/docker-build-and-push.md) | Docker Build and Push | ## Best Practices ### ✅ DO - Use container health checks - Set appropriate CPU and memory - Implement graceful shutdown - Use service accounts with least privilege - Monitor with Cloud Logging - Enable Cloud Armor for protection - Use revision management for blue-green deployments - Implement startup and liveness probes ### ❌ DON'T - Store secrets in code - Use default service account - Create stateful applications - Ignore health checks - Deploy without testing - Use excessive resource limits - Store files in container filesystem
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.