gcp-cloud-run
Specialized skill for building production-ready serverless applications on GCP. Covers Cloud Run services (containerized), Cloud Run Functions (event-driven), cold start optimization, and event-driven architecture with Pub/Sub.
Profile →npx skills add sickn33/agentic-awesome-skills --skill gcp-cloud-run --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Specialized skill for building production-ready serverless applications on GCP. Covers Cloud Run services (containerized), Cloud Run Functions (event-driven), cold start optimization, and event-driven architecture with Pub/Sub.
How it works
- Advocates using Cloud Run for containers and Cloud Run Functions for simple event handlers.
- Recommends startup CPU boost and min instances to optimize cold starts; suggests setting concurrency based on workload and starting at 8.
- Emphasizes including /tmp in memory planning and using VPC Connector only when needed; containers should be stateless and start fast; signals should be handled gracefully.
- Provides Cloud Run Service pattern with a Dockerfile example, a Node.js Express app, and a cloudbuild.yaml example to build, push, and deploy to Cloud Run with specific memory, CPU, min/max instances, concurrency, and cpu-boost settings; also shows a direct gcloud deploy command.
- Details Cloud Run Functions pattern with examples for HTTP, Pub/Sub, and Cloud Storage triggers, plus deployment commands for gen2 runtimes.
- Describes Cold Start Optimization Pattern including enabling startup CPU boost, setting min-instances, using a distroless image, lazy initialization of heavy dependencies, and increasing memory to trade for more CPU.
- Includes Concurrency Configuration and Node.js/Python specifics for achieving efficient concurrency, with examples illustrating async I/O and blocking operations.
- Documents Pub/Sub Integration Pattern for push subscriptions to Cloud Run, handling Pub/Sub push messages, and publishing messages to topics.
- Covers Cloud SQL Connection Pattern for securely connecting Cloud Run to Cloud SQL, with examples for Unix socket connections and environment variable configurations.
- Outlines Best practices for connection pooling, idle timeouts, error handling, and Cloud SQL Proxy consideration.
- Contains Secret Manager Integration guidance showing how to mount secrets as environment variables or files and how to access them, plus an example of Secret Manager API access.
- Presents Sharp Edges guidance about /tmp filesystem memory impact and stream processing vs buffering, with memory calculations and example code paths.
When to use it
- When building production-ready serverless apps on Google Cloud Platform using Cloud Run, Cloud Run Functions, Pub/Sub, and Cloud SQL.
What it can touch
- Tools explicitly referenced include gcloud, cloudbuild.yaml, Dockerfile, Node.js/Express code, Pub/Sub, and Secret Manager integration steps.
- Commands and file names are quoted exactly in the skill's instructions e.g., "Dockerfile", "cloudbuild.yaml", "gcloud run deploy", "gcloud functions deploy".
Caveats
- Risk level declared as critical. No licensing restrictions beyond MIT in the skill metadata.
- License stated: MIT.
- All guidance is directive and instructional; outcomes are not guaranteed by the skill itself.
# GCP Cloud Run Specialized skill for building production-ready serverless applications on GCP. Covers Cloud Run services (containerized), Cloud Run Functions (event-driven), cold start optimization, and event-driven architecture with Pub/Sub. ## Principles - Cloud Run for containers, Functions for simple event handlers - Optimize for cold starts with startup CPU boost and min instances - Set concurrency based on workload (start with 8, adjust) - Memory includes /tmp filesystem - plan accordingly - Use VPC Connector only when needed (adds latency) - Containers should start fast and be stateless - Handle signals gracefully for clean shutdown ## Patterns ### Cloud Run Service Pattern Containerized web service on Cloud Run **When to use**: Web applications and APIs,Need any runtime or library,Complex services with multiple endpoints,Stateless containerized workloads ```dockerfile # Dockerfile - Multi-stage build for smaller image FROM node:20-slim AS builder WORKDIR /app COPY package*.json ./ RUN npm ci --only=production FROM node:20-slim WORKDIR /app # Copy only production dependencies COPY --from=builder /app/node_modules ./node_modules COPY src ./src COPY package.json ./ # Cloud Ru
- Principles
- Patterns
- Cloud Run Service Pattern
- Structure
- Gclouddeploy
- Cloud Run Functions Pattern
- Cold Start Optimization Pattern
- 1. Enable Startup CPU Boost
- 2. Set Minimum Instances
- 3. Optimize Container Image
- 4. Lazy Initialize Heavy Dependencies
- 5. Increase Memory (More CPU)
- Optimizationimpact
- Concurrency Configuration Pattern
Deploy HTTP function gcloud functions deploy hello-http \ Deploy Pub/Sub function gcloud functions deploy process-messages \ Deploy Cloud Storage function gcloud functions deploy process-uploads \ gcloud run deploy my-service \ Higher memory = more CPU during startup Default concurrency is 80 Adjust based on your workload
What does the gcp-cloud-run skill do?
Specialized skill for building production-ready serverless applications on GCP. Covers Cloud Run services (containerized), Cloud Run Functions (event-driven), cold start optimization, and event-driven architecture with Pub/Sub.
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill gcp-cloud-run --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.