Gcp Gke Troubleshooting
CheckedProvides Google Cloud guidance and assistance for deploying and managing cloud infrastructure.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add dawiddutoit/custom-claude --skill gcp-gke-troubleshooting -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
dawiddutoit
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned dawiddutoit/custom-claude at 17b45a90a6.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 17b45a90a6
- Scanned
- 2 files, 501 lines
About this skill
What it does
This skill assists in troubleshooting issues within Google Kubernetes Engine (GKE) clusters. It can analyze error messages, identify potential causes of problems like pod failures or node instability, and suggest remediation steps based on common GKE operational patterns. The skill leverages knowledge of GKE architecture and best practices to provide targeted support for resolving cluster-related incidents.
When to use it
- You're experiencing persistent errors in your GKE pods and need help diagnosing the root cause.
- Your GKE nodes are frequently entering a NotReady state, impacting application availability.
- You’ve received an alert about resource exhaustion within your GKE cluster and want to understand how to address it.
- You're investigating performance degradation in your applications running on GKE and need assistance identifying bottlenecks.
Key capabilities
- Error message analysis
- Root cause identification for pod failures
- Troubleshooting node instability
- Resource exhaustion diagnosis
- Remediation suggestions
Example prompts
- "My GKE pod is failing with a 'CrashLoopBackOff' error. Can you help me troubleshoot it?"
- "I’m seeing high CPU utilization on my GKE nodes. What could be causing this?"
- "How do I diagnose why my Kubernetes deployment isn't scaling up as expected in GKE?"
Tips & gotchas
This skill assumes a basic understanding of Kubernetes and GKE concepts. Providing detailed error messages or logs will significantly improve the accuracy and relevance of its suggestions.