agentleFS
jpantsjohajpantsjoha/googlecloud-plugin/skills/cloud-run/SKILL.md

cloud-run

Skill4 starsChanged 4 months agoMITView on GitHub

Deploy and manage containerized workloads on Cloud Run. Covers service creation, traffic splitting, IAM, VPC connectivity, secrets integration, auto-scaling, and gcloud CLI patterns. Warns before billable deployments. Use when the user mentions: deploy to cloud run, create cloud run service, serverless container, scale cloud run, cloud run IAM, cloud run VPC, cloud run secrets, gcloud run.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    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
  1. Very specific:

    Never use --allow-unauthenticated without explicit intent and gcp-security sign-off

    line 62
  2. Very specific:

    Always specify --no-allow-unauthenticated as the default

    line 63

“Common” is measured: kept by at least 6 in 10 of the 4 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Cloud Run

Deploy and manage containerized applications on Google Cloud Run — fully managed, serverless, and scales to zero.

Prerequisites

  • gcloud CLI authenticated (gcloud auth login or ADC)
  • Project set: gcloud config set project PROJECT_ID
  • APIs enabled: gcloud services enable run.googleapis.com

Core Patterns

Deploy a container

# Billable action — confirm before running
gcloud run deploy SERVICE_NAME \
  --image IMAGE_URI \
  --region REGION \
  --platform managed \
  --no-allow-unauthenticated

Grant invoker access (least-privilege)

gcloud run services add-iam-policy-binding SERVICE_NAME \
  --region REGION \
  --member="serviceAccount:SA@PROJECT.iam.gserviceaccount.com" \
  --role="roles/run.invoker"

VPC connector (private connectivity)

gcloud run services update SERVICE_NAME \
  --vpc-connector CONNECTOR_NAME \
  --region REGION

Mount a secret

gcloud run services update SERVICE_NAME \
  --set-secrets=/path/to/secret=SECRET_NAME:latest \
  --region REGION

Safety Rules

  • Never use --allow-unauthenticated without explicit intent and gcp-security sign-off
  • Always specify --no-allow-unauthenticated as the default
  • Cost warning: Cloud Run bills per request and per CPU/memory allocated — estimate before deploying high-traffic services

References

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.