Install the "gcp-cloud-run" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/development/gcp-cloud-run into .claude/skills/gcp-cloud-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gcp-cloud-run", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add davila7/claude-code-templates --skill gcp-cloud-run -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "gcp-cloud-run" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/development/gcp-cloud-run into .agents/skills/gcp-cloud-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gcp-cloud-run", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add davila7/claude-code-templates --skill gcp-cloud-run -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "gcp-cloud-run" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/development/gcp-cloud-run into .cursor/skills/gcp-cloud-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gcp-cloud-run", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add davila7/claude-code-templates --skill gcp-cloud-run -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "gcp-cloud-run" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/development/gcp-cloud-run into .gemini/skills/gcp-cloud-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gcp-cloud-run", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add davila7/claude-code-templates --skill gcp-cloud-run -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "gcp-cloud-run" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/development/gcp-cloud-run into .github/skills/gcp-cloud-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gcp-cloud-run", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add davila7/claude-code-templates --skill gcp-cloud-run -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "gcp-cloud-run" agent skill from https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/development/gcp-cloud-run into .opencode/skills/gcp-cloud-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gcp-cloud-run", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
gcp-cloud-run
GitHub stars
32k
Used in
7 other repos
Token cost
~1.7k tokens
SKILL.md length
75 words
Files
1
Skills in repo
478
Repo updated
First seen
Licence
MIT
At a glance
Specialized skill for building production-ready serverless applications on GCP.
Works in 4 steps: Set Minimum Instances → Optimize Container Image → Lazy Initialize Heavy Dependencies → …
Tasks that involve Event-driven systems
SKILL.md covers Patterns, 2. Set Minimum Instances, 3. Optimize Container Image and 4. Lazy Initialize Heavy…, plus 1 more section
Calls gcloud
What it does
GCP Cloud Run is an agent skill from davila7/claude-code-templates. 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.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Backend & APIs, covering Event-driven systems, Containers and Serverless. It works with Cloud Run, Google Cloud, Docker and npm. The repository describes itself as: CLI tool for configuring and monitoring Claude Code. The licence is MIT.
When your agent uses it
Tasks that involve Event-driven systems
Tasks that involve Containers
Tasks that involve Serverless
Example prompts
“/gcp-cloud-run”
Requirements
Docker
Workflow steps
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 46b4d8b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gcloud
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gcloud, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
GCP Cloud Run loads about 1.7k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 75 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~60
When it runs· the whole SKILL.md, loaded when a task matches
~1.7k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Download SKILL.mdSave it as .claude/skills/gcp-cloud-run/SKILL.md (or your agent's skills folder).
name
gcp-cloud-run
description
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.
source
vibeship-spawner-skills (Apache 2.0)
GCP Cloud Run
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']
javascript
```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 Run uses PORT env variable
ENV PORT=8080
EXPOSE 8080
# Run as non-root user
USER node
CMD ["node", "src/index.js"]
### Cold Start Optimization Pattern
Minimize cold start latency for Cloud Run
**When to use**: ['Latency-sensitive applications', 'User-facing APIs', 'High-traffic services']
```javascript
## 1. Enable Startup CPU Boost
```bash
gcloud run deploy my-service \
--cpu-boost \
--region us-central1
2. Set Minimum Instances
bash
gcloud run deploy my-service \
--min-instances 1 \
--region us-central1
3. Optimize Container Image
dockerfile
# Use distroless for minimal image
FROM node:20-slim AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci --only=production
FROM gcr.io/distroless/nodejs20-debian12
WORKDIR /app
COPY --from=builder /app/node_modules ./node_modules
COPY src ./src
CMD ["src/index.js"]
4. Lazy Initialize Heavy Dependencies
javascript
// Lazy load heavy libraries
let bigQueryClient = null;
function getBigQueryClient() {
if (!bigQueryClient) {
const { BigQuery } = require('@google-cloud/bigquery');
bigQueryClient = new BigQuery();
}
return bigQueryClient;
}
// Only initialize when needed
app.get('/api/analytics', async (req, res) => {
const client = getBigQueryClient();
const results = await client.query({...});
res.json(results);
});
5. Increase Memory (More CPU)
bash
# Higher memory = more CPU during startup
gcloud run deploy my-service \
--memory 1Gi \
--cpu 2 \
--region us-central1
## Anti-Patterns
### ❌ CPU-Intensive Work Without Concurrency=1
**Why bad**: CPU is shared across concurrent requests. CPU-bound work
will starve other requests, causing timeouts.
### ❌ Writing Large Files to /tmp
**Why bad**: /tmp is an in-memory filesystem. Large files consume
your memory allocation and can cause OOM errors.
### ❌ Long-Running Background Tasks
**Why bad**: Cloud Run throttles CPU to near-zero when not handling
requests. Background tasks will be extremely slow or stall.
## ⚠️ Sharp Edges
| Issue | Severity | Solution |
|-------|----------|----------|
| Issue | high | ## Calculate memory including /tmp usage |
| Issue | high | ## Set appropriate concurrency |
| Issue | high | ## Enable CPU always allocated |
| Issue | medium | ## Configure connection pool with keep-alive |
| Issue | high | ## Enable startup CPU boost |
| Issue | medium | ## Explicitly set execution environment |
| Issue | medium | ## Set consistent timeouts |
We found 16 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 7 other GitHub owners. This page covers the copy in davila7/claude-code-templates, which our catalogue first saw on October 7, 2026.
GCP Cloud Run next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
GCP Cloud Run compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
GCP Cloud Run this skilldavila7/claude-code-templates
Create a deployable Polylith project with poly create project — a lightweight pyproject.toml under projects/<name/ that references bricks for deployment as a Docker image, wheel, AWS Lambda, GCP…
Automatically discover cloud, infrastructure, deployment, and container skills when working with AWS, GCP, Azure, Docker, Kubernetes, Terraform, Netlify, Heroku, serverless, or IaC
Fix false-positive Cloud Run deploys where gcloud builds submit --tag silently fails but the follow-up gcloud run services update --image :latest succeeds against a stale image, producing a…
Runs web-grounded searches through Perplexity's Sonar models over OpenRouter for current events, recent literature and cited facts beyond the model's training cutoff.
Analyzes Neuropixels recordings from SpikeGLX or Open Ephys through preprocessing, drift correction, Kilosort4 spike sorting, quality metrics and curation.
Guides corrective and preventive action (CAPA) work in a quality management system, from initiation and root cause analysis through effectiveness verification.
Specialized skill for building production-ready serverless applications on GCP. GCP Cloud Run is an agent skill from davila7/claude-code-templates. Specialized skill for building production-ready serverless applications on GCP.
When should I use GCP Cloud Run?
GCP Cloud Run fits situations like: tasks that involve Event-driven systems; tasks that involve Containers; tasks that involve Serverless.
How do I install GCP Cloud Run in Claude Code?
Run `npx skills add davila7/claude-code-templates --skill gcp-cloud-run -a claude-code`. Or copy the skill folder (cli-tool/components/skills/development/gcp-cloud-run in davila7/claude-code-templates) into .claude/skills/gcp-cloud-run in your project. Claude Code loads it when a task matches its description.
How do I install GCP Cloud Run in Codex?
Run `npx skills add davila7/claude-code-templates --skill gcp-cloud-run -a codex`. Or copy the skill folder (cli-tool/components/skills/development/gcp-cloud-run in davila7/claude-code-templates) into .agents/skills/gcp-cloud-run in your project. Codex loads it when a task matches its description.
Can I use GCP Cloud Run in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add davila7/claude-code-templates --skill gcp-cloud-run -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gcp-cloud-run, .gemini/skills/gcp-cloud-run, .github/skills/gcp-cloud-run and .opencode/skills/gcp-cloud-run in your project.
What does GCP Cloud Run need to run?
Going by SKILL.md and its folder, GCP Cloud Run needs the command-line tools its instructions call (gcloud). Our summary lists: Docker.
Does GCP Cloud Run access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is GCP Cloud Run safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does GCP Cloud Run use?
GCP Cloud Run is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does GCP Cloud Run use?
About 1.7k tokens (SKILL.md is roughly 6.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to GCP Cloud Run?
Skills that share tags, products or a category with GCP Cloud Run: Polylith Project Management (DavidVujic/python-polylith, 553 stars), Devops (nicepkg/auto-company, 194 stars), Logfire Infrastructure (pydantic/skills, 140 stars) and Deepgram Deploy Integration (jeremylongshore/tons-of-skills-marketplace, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains GCP Cloud Run?
davila7 (a GitHub user) maintains it in davila7/claude-code-templates, which has 32,483 GitHub stars. The repository holds 478 skills in this directory. The repository was last updated on October 9, 2026.
Source: davila7/claude-code-templates on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.