cloud-run-basics
Skill2 starsChanged 3 months agoApache-2.0View on GitHub
Use when a task involves deploying, configuring, troubleshooting, securing, scaling, or cost-optimizing Google Cloud Run services, jobs, or worker pools.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- oivanfelipe/claude-skillstheir own version, first seen Nov 8, 2026
- ManatoYamashita/skillstheir own version, first seen Nov 1, 2026
- olaitanojo/skillstheir own version, first seen Oct 17, 2026
- rittmananalytics/wire-plugintheir own version, first seen Oct 5, 2026
- google/skillstheir own version, first seen Sep 29, 2026
- Adhamxon/claude-code-skillstheir own version, first seen Jul 30, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- google/skills★ 24ksame name
- jmxt3/gitscape.ai★ 33same name
- rittmananalytics/wire-plugin★ 14same name
- Adhamxon/claude-code-skills★ 2same name
- ManatoYamashita/skills★ 1same name
- olaitanojo/skills★ 1same name
- oivanfelipe/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- adversarial-auditSkill
- architectSkill
- debuggingSkill
- design-reviewSkill
- executorSkill
- gap-analysisSkill
- github-workflowSkill
- optimizationSkill
- reliabilitySkill
- researchSkill
- reuse-firstSkill
- security-reviewSkill
- simplicitySkill
- verificationSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 8 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Treat Google Cloud account, project ID, region, resource type, service identity, current revision, exposure, and billing impact as explicit …
- Very specific: line 14
Before a consequential change, confirm the active account/project, region, target service/job/worker pool, current resource state, …
- Distinctive: line 16
Do not silently enable APIs, broaden IAM, make a service public, create infrastructure, trigger builds, or enable paid/unknown-cost …
- Distinctive: line 22
Prefer dedicated least-privilege service accounts and approved secret storage.
- Very specific: line 26
Prefer scale-to-zero for bursty workloads when requirements allow it.
- Distinctive: line 28
Do not add VPC connectors, NAT, load balancers, CDN, static IPs, Cloud SQL, GPUs, larger instances, or CI/CD as generic best practice.
- Distinctive: line 34
Prefer deterministic image inputs.
- Distinctive: line 40
Do not equate API/CLI success with application correctness.
- Distinctive: line 42
Stop on unresolved project/account identity, region/resource, write authority, exposure intent, destructive replacement, IAM expansion, …
- Distinctive: line 44
Before unfamiliar flags or Preview behavior, inspect current CLI help and official documentation.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Cloud Run Basics
Core invariant
Treat Google Cloud account, project ID, region, resource type, service identity, current revision, exposure, and billing impact as explicit live state. Read before write; do not trust old conversation or local defaults.
Pre-write gate
Before a consequential change, confirm the active account/project, region, target service/job/worker pool, current resource state, IAM/network/secrets/traffic effects, and authorization.
Do not silently enable APIs, broaden IAM, make a service public, create infrastructure, trigger builds, or enable paid/unknown-cost features merely to make deployment easier.
Runtime and identity
HTTP containers must listen on 0.0.0.0:$PORT. Use services for request/event workloads, jobs for run-to-completion work, and worker pools for continuous pull-based processing.
Prefer dedicated least-privilege service accounts and approved secret storage. Never place credentials in source-controlled files or command history. Public invocation must be explicit.
Cost and infrastructure
Prefer scale-to-zero for bursty workloads when requirements allow it. Keep min-instances=0 unless availability/latency justifies always-on capacity, and bound max-instances when fan-out can create cost or downstream pressure.
Do not add VPC connectors, NAT, load balancers, CDN, static IPs, Cloud SQL, GPUs, larger instances, or CI/CD as generic best practice. Verify current Google Cloud pricing when cost matters; do not assume a short operation is free.
gcloud run deploy --source may invoke Cloud Build and create artifacts. Treat it as cloud execution with IAM and billing effects.
Deployment and verification
Prefer deterministic image inputs; immutable digests are useful for controlled releases. Run repository-designated checks before deployment when available.
Flow:
inspect -> verify app -> review config/cost -> deploy -> inspect revision -> verify health/auth -> verify traffic
Do not equate API/CLI success with application correctness. Keep local tests, image correctness, deploy success, revision health, traffic behavior, application acceptance, security, and cost review separate.
Stop on unresolved project/account identity, region/resource, write authority, exposure intent, destructive replacement, IAM expansion, paid/unknown-cost operation without approval, or required verification failure.
Before unfamiliar flags or Preview behavior, inspect current CLI help and official documentation.
Upstream
Adapted from Google Cloud Run skill guidance, with additional fail-closed identity, IAM, cost, and verification rules for agent-driven workflows.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.