gcp
Skill0 starsChanged 6 months agoMITView on GitHub
Operate GCP and GKE clusters using gcloud and kubectl. Fill in your cluster map below. Primary namespace: <your-namespace> (typically the same across all environments) Default context for production investigations: prod unless otherwise specified. See references/kubectl-patterns.md for context switching, log fetching, deployment inspection, secret syncing, and other day-to-day operational commands. If you hit a "I can't reach environment X" wall: This takes about 30 seconds and most "permission denied" issues turn out to be missing contexts, not actual permission gaps.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- darknecrocities/SkillBuildertheir own version, first seen Nov 1, 2026
- TheEdoRan/skillstheir own version, first seen Oct 15, 2026
- Ultimate-Alchemy/claude-skillstheir own version, first seen Oct 15, 2026
- G1Joshi/Agent-Skillstheir own version, first seen Oct 13, 2026
- conjure-3301/skillstheir own version, first seen Aug 17, 2026
- muxammadmamajonov/dot-claudetheir own version, first seen Jul 6, 2026
Used with
Projects with it also use firebase.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
xfstudioSkillfirebase
Firebase gives you a complete backend in minutes - auth, database, storage, functions, hosting. But the ease of setup hides real complexity. Security rules are your last line of defense, and they're often wrong. Firestore queries are limited, and you learn this after you've designed your data model. This skill covers Firebase Authentication, Firestore, Realtime Database, Cloud Functions, Cloud Storage, and Firebase Hosting. Key insight: Firebase is optimized for read-heavy, denormalized data. I
Also in 3 projects that use this
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- G1Joshi/Agent-Skills★ 15same name
- darknecrocities/SkillBuilder★ 13same name
- ffsshhttiikk/opencode-agents-skills★ 2same name
- conjure-3301/skills★ 0same name
- muxammadmamajonov/dot-claude★ 0same name
- TheEdoRan/skills★ 0same name
- Ultimate-Alchemy/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.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 45
If you hit a "I can't reach environment X" wall:
“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
GCP / Kubernetes Skill — TEMPLATE
Operate GCP and GKE clusters using
gcloudandkubectl. Fill in your cluster map below.
Cluster Map
| Alias | Context Name | Project | Region | Nodes | Use |
| prod | <your-prod-context> | <your-prod-project> | <region> | <n> | Production |
| preprod | <your-preprod-context> | <your-preprod-project> | <region> | <n> | Preproduction |
| qa | <your-qa-context> | <your-qa-project> | <region> | <n> | QA |
| sit | <your-sit-context> | <your-sit-project> | <region> | <n> | System Integration Testing |
| dev | <your-dev-context> | <your-dev-project> | <region> | <n> | Dev |
Primary namespace: <your-namespace> (typically the same across all environments)
Default context for production investigations: prod unless otherwise specified.
Authentication
# Check current auth
gcloud auth list
# Re-authenticate if token expired
gcloud auth login
# Switch to a cluster context
kubectl config use-context <your-prod-context>
# Fetch credentials for a cluster (if context not yet in kubeconfig)
gcloud container clusters get-credentials <cluster-name> \
--project <project-id> \
--region <region>Common Patterns
See references/kubectl-patterns.md for context switching, log fetching, deployment inspection, secret syncing, and other day-to-day operational commands.
Missing Contexts
If you hit a "I can't reach environment X" wall:
- Find the GCP project:
gcloud projects list | grep -i <env> - List clusters in it:
gcloud container clusters list --project <project> - Add credentials:
gcloud container clusters get-credentials <cluster> --region <region> --project <project> - Verify:
kubectl config get-contexts
This takes about 30 seconds and most "permission denied" issues turn out to be missing contexts, not actual permission gaps.
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.