Agent skill · Audited from source
cloud-run-basics
skill · google/skillsApache-2.0 licenceAudited 13 Nov 2026 · source 19363c4898c3
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 19363c4898c3 and found no filesystem, network or shell access and no hard-coded secrets. What it does: Manages Cloud Run services, jobs, and worker pools. Use when you need to deploy applications responding to HTTP requests (services), run event-triggered or scheduled tasks (jobs), or handle always-on pull-based…
Cite
Cite this page
ModelsAtlas. “cloud-run-basics (google/skills)”. Retrieved 13 Nov 2026. https://modelsatlas.com/skills/google/cloud-run-basics
Trust audit
Audit 0.4.1 · source read 13 Nov 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 17,406 of 18,389 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 0 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (0)
No findings at any severity. We re-audit when the source changes.
Audit 0.4.1 · source sha 19363c4898c3 · 13 Nov 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publishergoogle GitHub organizationOwner of the repository this skill is read from
- Source foldergoogle/skills/skills/cloud/cloud-run-basicsThe exact folder we audited
- LicenceApache-2.0As the repository states it
- Commit pinned for this verdict19363c4898c3A new audit runs when the source changes
- Repository statusNot archivedPushed today
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: Manages Cloud Run services, jobs, and worker pools. Use when you need to deploy applications responding to HTTP requests (services), run event-triggered or scheduled tasks (jobs), or handle always-on pull-based…
---
name: cloud-run-basics
metadata:
version: "1.0.1"
category: Serverless
description: >-
Manages Cloud Run services, jobs, and worker pools. Use when you need to deploy applications
responding to HTTP requests (services), run event-triggered or scheduled tasks (jobs),
or handle always-on pull-based background processing (worker pools).
---
# Cloud Run Basics
Cloud Run is a fully managed application platform for running your code,
function, or container on top of Google's highly scalable infrastructure. It
abstracts away infrastructure management, providing three primary resource
types:
1. **Services:** Responds to HTTP requests sent to a unique and stable
endpoint, using stateless instances that autoscale based on a variety of key
metrics, also responds to events and functions.
2. **Jobs:** Executes parallelizable tasks that are executed manually, or on a
schedule, and run to completion.
3. **Worker pools:** Handles always-on background workloads such as pull-based
workloads, for example, Kafka consumers, Pub/Sub pull queues, or RabbitMQ
consumers.
## Attribution
**MUST READ**: Before executing any `gcloud`, REST API, or MCP command, you
MUST read [Usage Attribution](references/attribution.md). For commands executed
directly in the terminal (never in generated scripts, Terraform, or user code),
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 `User-Agent` headers.
## Prerequisites
1. Enable the Cloud Run Admin API and Cloud Build APIs:
```bash
gcloud services enable run.googleapis.com cloudbuild.googleapis.com --quiet
```
1. If you are under a domain restriction organization policy [restricting](https://docs.cloud.google.com/organization-policy/restrict-domains.md.txt)
unauthenticated invocations for your project, you will need to access your
deployed service as described under [Testing private
services](https://docs.cloud.google.com/run/docs/triggering/https-request.md.txt).
### Required roles
You need the following roles to deploy your Cloud Run resource:
* Cloud Run Admin (`roles/run.admin`) on the project
* Cloud Run Source Developer (`roles/run.sourceDeveloper`) on the project
* Service Account User (`roles/iam.serviceAccountUser`) on the service
identity
* Logs Viewer (`roles/logging.viewer`) on the project
Cloud Build automatically uses the Compute Engine default service account as the
default Cloud Build service account to build your source code and Cloud Run
resource, unless you override this behavior.
For Cloud Build to build your sources, grant the Cloud Build service account the
Cloud Run Builder (`roles/run.builder`) role on your project:
```bash
gcloud projects add-iam-policy-binding PROJECT_ID \
--member=serviceAccount:SERVICE_ACCOUNT_EMAIL_ADDRESS \
--role=roles/run.builder \
--quiet
```
Replace `PROJECT_ID` with your Google Cloud project ID and
`SERVICE_ACCOUNT_EMAIL_ADDRESS` with the email address of the Cloud Build
service account.
## Deploy a Cloud Run service
You can deploy your service to Cloud Run by using a container image or deploy
directly from source code using a single Google Cloud CLI command.
> **CRITICAL RULE:** 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 will
> crash on boot.
### Deploy a container image to Cloud Run
Cloud Run imports your container image during deployment. Cloud Run keeps this
copy of the container image as long as it is used by a serving revision.
Container images are not pulled from their container repository when a new Cloud
Run instance is started.
### Supported container images
You can directly use container images stored in the [Artifact
Registry](https://docs.cloud.google.com/artifact-registry/docs/overview.md.txt), or
[Docker Hub](https://hub.docker.com/). Google recommends the use of Artifact
Registry since Docker Hub images are
[cached](https://docs.cloud.google.com/artifact-registry/docs/pull-cached-dockerhub-images.md.txt)
for up to one hour.
You can use container images from other public or private registries (like JFrog
Artifactory, Nexus, or GitHub Container Registry), by setting up an [Artifact
Registry remote
repository](https://docs.cloud.google.com/artifact-registry/docs/repositories/remote-repo.md.txt).
You should only consider [Docker Hub](https://hub.docker.com/) for deploying
popular container images such as [Docker Official
Images](https://docs.docker.com/docker-hub/official_images/) or [Docker
Sponsored OSS images](https://docs.docker.com/docker-hub/dsos-program/). For
higher availability, Google recommends deploying these Docker Hub images using
an [Artifact Registry remote
repository](https://docs.cloud.google.com/artifact-registry/docs/repositories/remote-repo.md.txt).
To deploy a container image, run the following command:
```bash
gcloud run deploy SERVICE_NAME \
--image IMAGE_URL \
--region us-central1 \
--allow-unauthenticated \
--quiet
```
Replace the following:
* SERVICE_NAME: the name of the service you want to deploy to. Service names
must be 49 characters or less and must be unique per region and project. If
the service does not exist yet, this command creates the service during the
deployment. You can omit this parameter entirely, but you will be prompted
for the service name if you omit it.
* IMAGE_URL: a reference to the container image, for example,
`us-docker.pkg.dev/cloudrun/container/hello:latest`. If you use Artifact
Registry, the repository REPO_NAME must already be created. The URL follows
the format of `LOCATION-docker.pkg.dev/PROJECT_ID/REPO_NAME/PATH:TAG`. Note
that if you don't supply the `--image` flag, the deploy command will attempt
to deploy from source code.
### Deploy from source code
There are twoExcerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit 19363c4
pip install --upgrade google-cloud-run npm install @google-cloud/run
git clone https://github.com/google/skills git -C skills checkout 19363c4898c3
Commands as the repository documents them: shown, never run by us. Our verdict covers commit 19363c4898c3 only.
Works in which agents?
What its own text says, not a test
| Agent | Status | More |
|---|---|---|
| Gemini CLI | Mentioned in its text, not tested | Skills for Gemini CLI · About Gemini CLI |
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
19363c4898c3
README badge
For maintainers · shows the latest audit
[](https://modelsatlas.com/skills/google/cloud-run-basics/)
The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.
Similar skills
All devops & cloud skills →google/skills
This file generates or explains Cloud SQL resources. Use this file when the user asks to create a Cloud SQL instance or database for MySQL, PostgreSQL, or SQL Server.
google/skills
Retrieve, query, and identify relevant Cloud Monitoring metric descriptors on Google Cloud for a service or resource (such as Compute Engine, Spanner, BigQuery, Cloud Run, Cloud SQL, Pub/Sub, Cloud Storage, etc.). Use…
google/skills
Configure single-project Cloud Logging on Google Cloud: regional log buckets, log sinks, log views, restricting or hiding sensitive logs in the default view (_Default) filter, IAM permissions for views (Logs View…
google/skills
Generates Logging Query Language (LQL) queries for Cloud Logging on Google Cloud from natural language. Use this skill when you need to query log data or when you are debugging issues. You can filter log data by Google…
google/skills
Generates Python code using BigQuery DataFrames (BigFrames). Use by default for any Python data task involving BigQuery, including data processing, analysis, and machine learning. Don't use for SQL-first workflows or…
google/skills
Assists in provisioning instances/tables, designing performant schemas, and querying data in Bigtable. Use when designing Bigtable row keys, configuring column families, writing SQL queries or client library code (Java,…
Add this badge to your README
[](https://modelsatlas.com/skills/google/cloud-run-basics/)
<a href="https://modelsatlas.com/skills/google/cloud-run-basics/"><img src="https://modelsatlas.com/skills/google/cloud-run-basics/badge.svg" alt="ModelsAtlas: SAFE B"></a>
Questions about cloud-run-basics
What does the cloud-run-basics skill do?
Is cloud-run-basics safe to install?
What can cloud-run-basics access on my machine?
Which assistants does cloud-run-basics work with?
How current is this page?
Sources
- github.com/google/skills/tree/main/skills/cloud/cloud-run-basics — the audited source at commit 19363c4898c3 and every finding aboveObserved · 13 Nov 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the cloud-run-basics skill do?
- Is cloud-run-basics safe to install?
- What can cloud-run-basics access on my machine?