← Search

Cloud Run basics: deploy services, jobs and worker pools
Cloud 🧪 Install ran in our test sandbox · Nov 18, 2026 📌 Pinned version: commit 22bf5d1
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: a Google Cloud project with billing enabled (free…

Cloud Run basics: deploy services, jobs and worker pools

Manage Cloud Run services, jobs and worker pools — deploy from source or image, IAM, networking, cost optimization, troubleshooting

At a glance
What
Manage Cloud Run services, jobs and worker pools — deploy from source or image, IAM, networking, cost optimization, troubleshooting
Cost
Free
Needs
a Google Cloud project with billing enabled (free tier covers generous quotas) and the gcloud CLI installed
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version: 1.0.1

Quick answer

Cloud Run basics is a free Muse skill, for Cloud Run. It covers the three resource types: services responding to HTTP, jobs running to completion on manual or scheduled triggers, and worker pools for always-on pull-based background work. It also covers deploying from a container image or directly from source, plus IAM, networking, cost optimization and troubleshooting.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 18, 2026📌 Pinned version: commit 22bf5d1

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Google Cloud project with billing enabled (free tier covers generous quotas) and the gcloud CLI installed Install "Cloud Run basics: deploy services, jobs and worker pools" for me. Give my agent Google's official Cloud Run guide (version 1.0.1) — the three resource types (services responding to HTTP, jobs running to completion on manual or scheduled triggers, worker pools for always-on pull-based background work), deploying from a container image or directly from source with `gcloud run deploy` (buildpacks, Dockerfile, or no-build preview), creating and executing jobs with tasks/retries/timeouts/parallelism flags, deploying worker pools, the required IAM roles, and a reference directory (core concepts, CLI usage, client libraries, MCP usage, Terraform IaC, IAM & security, networking and cost optimization). Its critical rule is worth knowing cold: any deployed code must listen on `0.0.0.0` and use the injected `$PORT` (defaults to 8080), or it crashes on boot. Deployment-failure guidance is built in (read logs immediately on crash-on-boot, switch to buildpacks for native-dependency errors). Apache-2.0 licensed. Repository: https://raw.githubusercontent.com/google/skills/22bf5d15d546318171a1a27dda7fcdff9cb3029b/skills/cloud/cloud-run-basics/SKILL.md (the skill is the skills/cloud/cloud-run-basics/ folder at that commit: SKILL.md and the references/ folder with attribution.md, cli-usage.md, client-library-usage.md, core-concepts.md, iac-usage.md, iam-security.md, mcp-usage.md, and networking.md) Pinned version: install the code at commit 22bf5d15d546318171a1a27dda7fcdff9cb3029b exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. [FINGERPRINTS] Files at the pinned commit, from Skill Harbor's review of 2026-10-20: - SKILL.md: SHA-256 8bf95426fb0c74b7f4e1a66d906791f59c143959e8bc7205c9249ada00e24903, 16,308 bytes, 16,306 characters - references/attribution.md: SHA-256 98430e3a22ad85719cd51d6eae0ea04c9ecfd1cd424431e4a5c562ebbd803d70, 1,888 bytes, 1,886 characters - references/cli-usage.md: SHA-256 87a58f1c49b848f66fa6bf1e30882fe247232aa1bf76e90987abf5e8b031580e, 2,482 bytes, 2,482 characters - references/client-library-usage.md: SHA-256 2f2c95b3fe6b8c36cfea903644279abe129816a84785739d4ba49e6bb571e772, 3,470 bytes, 3,470 characters - references/core-concepts.md: SHA-256 459830cc25d643dfd255b127df4df01bf9987b9eafd5c8aa8baca054517ccffe, 6,709 bytes, 6,709 characters - references/iac-usage.md: SHA-256 429c3a3edba4bd108c5faea064fdd17f13fddc3fd2238a245de0c700d29d940c, 2,020 bytes, 2,020 characters - references/iam-security.md: SHA-256 9430085095a0d16243ef7b8eb5a875690df633f8626078d3b004387bae2a7721, 5,342 bytes, 5,342 characters - references/mcp-usage.md: SHA-256 ad9aecf215e01dc4384918b39457a118d15d16f3f6c7e10aa80a50a686eca780, 1,907 bytes, 1,907 characters - references/networking.md: SHA-256 8a62caf6ae07721c77d384ec30991df7349ebc674fb8152d58dcad216527866c, 5,909 bytes, 5,909 characters If any of these does not match, it changed since the review: do not install it yet, tell me what you found and let me decide. Updated October 20, 2026: Skill Harbor regenerated this install prompt from the current upstream files, at version 1.0.1 (the previous prompt described version 1.0.0 and fetched SKILL.md alone). In SKILL.md itself, the only change besides the version number is a new Attribution section: before executing any direct `gcloud`, REST API, or MCP command, the agent must read references/attribution.md; for commands executed directly in the terminal, prefix `gcloud` with CLOUDSDK_METRICS_REQUEST_ATTRIBUTION="agent-skills/1.0 (skill:cloud-run-basics)" and append `agent-skills/1.0 (skill:cloud-run-basics)` to the User-Agent header of direct calls. That tagging applies only to commands executed directly in the terminal — never in generated scripts, Terraform, or user code — and it must not be persisted via `gcloud config set` (the prefix is inline, per command). The tag identifies only the skill and its version; it carries no user data, and references/attribution.md documents a user opt-out: if the user asks to disable or remove tracking or attribution tags, omit the CLOUDSDK_METRICS_REQUEST_ATTRIBUTION variable and the custom User-Agent suffix from all commands. This prompt also changes the installation itself: it now installs the complete skill folder, SKILL.md plus the whole references/ folder, instead of SKILL.md alone. What is sent, and when: nothing is sent anywhere and nothing is executed during installation itself — installing only downloads the pinned folder from GitHub and copies it. Sending starts later, when you use the skill, through your own authenticated gcloud CLI against your own Google Cloud project, as described in the safety check below. 1. Fetch the whole skills/cloud/cloud-run-basics/ folder at the pinned commit into a temporary folder, then compare SKILL.md and all eight references/ files with the fingerprints from Skill Harbor's review of 2026-10-20 (see [FINGERPRINTS] above). If any does not match, do not install it yet, tell me what you found and let me decide. 2. Safety check: read SKILL.md and the references/ files and review them for anything suspicious (unexpected network calls, shell commands, credential harvesting); STOP on any red flag and tell me. Tell me in plain words what the skill does when used, which services it connects to, whether it reads or sends any personal information or keys, and anything that seems unusual. Confirm these points from the files: - The skill is instructions plus references — nine Markdown files, no bundled scripts and no background service, and nothing runs on its own. Nothing is sent anywhere and nothing is executed during installation itself. Everything below happens in use, when I ask for Cloud Run work. - In use, the skill works through my own authenticated gcloud CLI against my own Google Cloud project: deploying services, jobs and worker pools, reading logs, and applying the IAM and networking guidance in the references. Real Google Cloud usage can result from the deploys I ask for (the free tier covers generous quotas, 2M requests/month, but billing must be enabled on the project). - Prerequisites and roles, from SKILL.md: enable the Cloud Run Admin API and the Cloud Build API (`gcloud services enable run.googleapis.com cloudbuild.googleapis.com`); the deploying identity needs Cloud Run Admin (roles/run.admin), Cloud Run Source Developer (roles/run.sourceDeveloper), Service Account User (roles/iam.serviceAccountUser) on the service identity, and Logs Viewer (roles/logging.viewer); the Cloud Build service account needs Cloud Run Builder (roles/run.builder) to build sources. - The critical rule and the failure guidance: any deployed code must listen on 0.0.0.0 (not 127.0.0.1) and use the injected $PORT environment variable (defaults to 8080), or it crashes on boot. On failure: for an IAM or permission error, read references/iam-security.md; on crash-on-boot or a failed healthcheck, fetch the logs immediately with `gcloud logging read` to find the exact runtime error; on a native dependency error with --no-build, switch to `--source .` (buildpacks) to compile native extensions properly for Linux. - Attribution, new in this version: SKILL.md orders the agent to read references/attribution.md before executing any `gcloud`, REST API, or MCP command. That file says to tag every command executed directly in the terminal: prefix every `gcloud` invocation, whatever the subcommand, inline with CLOUDSDK_METRICS_REQUEST_ATTRIBUTION="agent-skills/1.0 (skill:cloud-run-basics)" (set inline on each command because shell state may not persist, and never persist it via `gcloud config set`, which would mislabel unrelated usage), and on direct HTTP, REST, or MCP requests, append `agent-skills/1.0 (skill:cloud-run-basics)` to the User-Agent header (append to an existing User-Agent rather than overwriting it). The tag identifies only the skill and its version and carries no user data. Its scope is commands executed directly in the terminal only: never include the prefix or suffix in generated scripts, Terraform templates, or code given to the user for their own repositories. A user opt-out is documented: if I ask to disable or remove tracking or attribution tags, omit the variable and the User-Agent suffix from all commands. - Credentials: the repo contains no secrets in code; credentials come only from my own gcloud authentication, via the secure vault or environment variables — never pasted into the chat. 3. When I say "yes, install", install it as a skill: copy the whole fetched skills/cloud/cloud-run-basics/ folder (SKILL.md and references/, keeping the references/ subfolder so the relative links in SKILL.md keep working) into the agent's skills directory, in a folder named "google-skills-cloud-run-basics". 4. Verify with no network calls: frontmatter valid, files in place, and the copied SKILL.md still matches its fingerprint above. 5. Report what was installed, where, and what I still need to do myself (e.g. enable the Cloud Run Admin and Cloud Build APIs on my project, and make sure the deploying identity and the Cloud Build service account hold the roles listed in the safety check). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit 22bf5d1 · 2026-10-20
🧪 Install ran in our test sandbox · Nov 18, 2026
👁 Observed during the install test · Nov 18, 2026 : no network contact
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
22bf5d1 · 2026-10-20
Sandbox install test
Install ran in our test sandbox · Nov 18, 2026
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : No commands, network calls, packages, file writes or API keys detected.

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.