# Build Production-Ready Cloud Run Applications

Cloud Run projects often fail on scaling, startup, networking, and resource constraints. This skill provides deployment patterns and troubleshooting guidance for resilient serverless services.

## Install

```bash
npx skillstore add sickn33/gcp-cloud-run
```

## Metadata

- Status: approved
- Slug: sickn33-gcp-cloud-run
- Skillstore revision: r2
- Version status: missing
- Tree hash: 616703c810761dac8266e9364e2f0d48792e96f4cc37ea251aa1e6fd0475476c
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/gcp-cloud-run
- Ref: 88a8e9a07f4c54ab105c1c41b6267c287146b07b
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, filesystem, env\_access
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/sickn33-gcp-cloud-run
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-gcp-cloud-run/manifest

## Capabilities

- Designs Cloud Run services and event-driven functions for Node.js and Python workloads.
- Provides Dockerfile, Cloud Build, and gcloud deployment patterns.
- Explains Pub/Sub, Cloud Tasks, Cloud SQL, and Secret Manager integrations.
- Tunes cold starts, concurrency, CPU allocation, memory, and instance scaling.
- Diagnoses runtime constraints involving temporary storage, VPC connections, startup, and request timeouts.

## Use Cases

- Deploy an Application Service: Create a container, health endpoint, deployment configuration, and scaling plan for an existing web application.
- Build a Serverless Platform Pattern: Connect Cloud Run with Pub/Sub, Cloud SQL, Secret Manager, or Cloud Tasks using production-oriented configuration.
- Resolve Cloud Run Failures: Investigate cold starts, memory exhaustion, connection resets, startup failures, and timeout mismatches.

## Prompt Templates

### Prepare a Basic Deployment

```
Prepare a Cloud Run deployment plan for my [language] service in [region]. Include container requirements, PORT handling, health checks, and a gcloud command.
```

### Create an Event Handler

```
Design a Cloud Run Function for [event source]. Include deployment settings, payload handling, retries, authentication, and failure behavior.
```

### Tune Performance and Cost

```
Review this workload profile: [traffic, latency, CPU, memory]. Recommend concurrency, minimum instances, CPU allocation, memory, timeouts, and measurement steps.
```

### Review a Production Architecture

```
Assess this Cloud Run architecture: [details]. Identify reliability, IAM, secret, network, database, scaling, and observability risks. Prioritize concrete remediations.
```

## Limitations

- It provides guidance and examples but does not deploy or inspect GCP resources automatically.
- Example names, regions, endpoints, and credentials require environment-specific replacement.
- Security-sensitive examples require IAM, authentication, input validation, and network review.
- It focuses on Google Cloud Run and does not cover equivalent AWS or Azure services.

## Best Practices

- Measure workload behavior before changing concurrency, instance, CPU, or memory settings.
- Use least-privilege service accounts and Secret Manager for sensitive configuration.
- Validate authentication, inputs, retries, timeouts, and shutdown behavior before production deployment.

## Anti Patterns

- Do not copy placeholder commands into production without reviewing project, region, identity, and exposure settings.
- Do not store large working files in temporary storage without accounting for memory.
- Do not accept unauthenticated events or caller-controlled callback destinations without strict validation.

## Security Audit

- Audited at: 2026-07-23T23:15:57.861\+00:00
- Summary: All 164 static matches are false positives caused by Markdown fences, illustrative template literals, and benign cloud configuration examples. Three semantic risks remain in the examples: unauthenticated Pub/Sub processing, callback URL SSRF, and reflected HTML injection.

## Stats

- Views: 100
- Downloads: 11
- Favorites: 0
- Popularity score: 0