Gcp
A comprehensive skill catalog for AI agents
npx -y skills add G1Joshi/Agent-Skills --skill gcpAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 10 stars10 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Google Cloud Platform with Cloud Run, GKE, and BigQuery. Use for GCP infrastructure.
SKILL.md
1.4 KB, 312 tokens by cl100k_base, as published. Nobody here has run it
Google Cloud Platform (GCP)
GCP is known for its data analytics (BigQuery) and being the home of Kubernetes. 2025 highlights Vertex AI for rapid model deployment and Cloud Run for serverless everywhere.
When to Use
- Big Data: BigQuery is arguably the best data warehouse for speed and ease of use.
- Kubernetes: GKE (Google Kubernetes Engine) often leads in features and stability (Autopilot).
- AI: TPU access and Vertex AI for training large models.
Core Concepts
Projects
The primary unit of isolation. Resources belong to a Project. Projects belong to Folders/Organization.
Global VPC
Unlike AWS/Azure, GCP VPCs are global. Subnets are regional. A single VPC can span the world.
IAM
Permissions are granted to Members (Users/Service Accounts) on Resources via Roles.
Best Practices (2025)
Do:
- Use Cloud Run: The default computed choice for stateless containers. Scales to zero, fast startup.
- Use Workload Identity: Let GKE workloads impersonate Service Accounts securely.
- Shared VPC: For orgs, use a Shared VPC in a Host Project to centralize networking.
Don't:
- Don't use
ownerrole: It's too broad. Use precise roles (storage.objectViewer).
References
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most containers cloud skills give in 312 tokens
Counted across 607 of the 657 authors here whose files we hold, read 2026-08-07
- Run containers as a non-root userin 66 of 607, across 46 files
- Use multi-stage buildsin 53 of 607, across 44 files
- Use Promise.all for independent operationsin 47 of 607, across 13 files
- Import directly instead of barrel filesin 46 of 607, across 12 files
- Use ternary instead of AND for conditionalsin 45 of 607, across 12 files
- Use Set or Map for O(1) lookupsin 42 of 607, across 10 files
- Create a .dockerignore filein 41 of 607, across 31 files
- Read individual rule files for detailsin 39 of 607, across 9 files
- Copy dependency files before source codein 36 of 607, across 23 files
- Authenticate server actions like API routesin 35 of 607, across 7 files
- Use next/dynamic for heavy componentsin 34 of 607, across 9 files
- Use React.cache for per-request deduplicationin 34 of 607, across 10 files
Said here and by no other author read
- use Cloud Run for stateless containers
- use Workload Identity for GKE workloads
- use a Shared VPC to centralize networking
- assign precise IAM roles
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.