gcp-cloud-run
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.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "gcp-cloud-run" from https://skillstore.io/skills/sickn33-gcp-cloud-run.md and its manifest at https://skillstore.io/api/skills/sickn33-gcp-cloud-run/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "gcp-cloud-run". Plan a Node.js API deployment with low cold-start latency.
Expected outcome:
- Use a small production image and run as a non-root user.
- Enable startup CPU boost and begin with one minimum instance.
- Measure latency before adjusting concurrency, CPU, and memory.
- Add readiness behavior and graceful SIGTERM handling.
Using "gcp-cloud-run". Explain why a service fails after writing a large temporary file.
Expected outcome:
Cloud Run stores temporary files in memory. Stream the object or use Cloud Storage, then size memory for unavoidable temporary data.
Using "gcp-cloud-run". Review a Pub/Sub push integration.
Expected outcome:
- Authenticate push delivery with a dedicated service account.
- Validate the token audience and calling identity.
- Return success only after durable processing.
- Configure retries and a dead-letter topic.
Security Audit
High RiskAll 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.
Confirmed security concerns (3)
Risk Factors
โ๏ธ External commands (50)
๐ Network access (6)
๐ Filesystem access (6)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-gcp-cloud-run/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-gcp-cloud-run?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-gcp-cloud-run?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-gcp-cloud-run/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-gcp-cloud-run.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
sickn33. (2026). gcp-cloud-run security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-gcp-cloud-run/audits/5BibTeX citation
@techreport{sickn33-sickn33-gcp-cloud-run-2026,
author = {sickn33},
title = {gcp-cloud-run security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-gcp-cloud-run/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "gcp-cloud-run security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/sickn33-gcp-cloud-run/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-gcp-cloud-run:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
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.
Try These Prompts
Prepare a Cloud Run deployment plan for my [language] service in [region]. Include container requirements, PORT handling, health checks, and a gcloud command.
Design a Cloud Run Function for [event source]. Include deployment settings, payload handling, retries, authentication, and failure behavior.
Review this workload profile: [traffic, latency, CPU, memory]. Recommend concurrency, minimum instances, CPU allocation, memory, timeouts, and measurement steps.
Assess this Cloud Run architecture: [details]. Identify reliability, IAM, secret, network, database, scaling, and observability risks. Prioritize concrete remediations.
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.
Avoid
- 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.