Kubernetes Operations
ListedAutomates Kubernetes cluster management tasks like deployments, scaling, and monitoring via a streamlined interface.
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 nodnarbnitram/claude-code-extensions --skill kubernetes-operations -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
nodnarbnitram
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 failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No credential access: failed
Touches credential material in 2 places.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
What it found
- .claude/skills/kubernetes-operations/SKILL.md:302Kubernetes credentials
cat ~/.kube/config - plugins/cce-kubernetes/skills/kubernetes-operations/SKILL.md:302Kubernetes credentials
cat ~/.kube/config
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 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 nodnarbnitram/claude-code-extensions at 35e7f7deae.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 35e7f7deae
- Scanned
- 16 files, 2,600 lines
- Copies in repo
- 2 — all of them scanned
About this skill
What it does
This skill provides comprehensive assistance for managing Kubernetes clusters using kubectl. It streamlines common tasks like debugging, resource management, and cluster operations through token-efficient scripts, preventing frequent errors and significantly reducing token usage (up to 70% savings in some cases). The skill focuses on providing concise summaries of information, avoiding verbose output that can flood the context.
When to use it
This skill is helpful when:
- You need to debug a Kubernetes pod quickly and efficiently.
- You want to list resources within your cluster without excessive verbosity.
- You require a rapid overview of your cluster's health status.
- You are performing operations in production environments and want to avoid common pitfalls.
- You encounter issues like
CrashLoopBackOff,ImagePullBackOff, or pods stuck in aPendingstate.
Key capabilities
- Provides token-efficient scripts for Kubernetes operations.
- Combines
kubectl describe, logs, and events into condensed summaries for debugging. - Offers quick overviews of node status and unhealthy pods.
- Prevents common errors like running commands in the wrong namespace or exposing secrets.
- Includes scripts for pod debugging (
debug_pod.py) and cluster health checks (cluster_health.py).
Example prompts
- "Debug this pod:
<pod-name>in namespace<namespace>." - "Check the overall health of my Kubernetes cluster."
- "List all pods in the current context."
Tips & gotchas
- Verify Context: Always confirm your
kubectlcontext usingkubectl config current-contextbefore performing any operations. - Explicit Namespace: Always specify the namespace with
-n <namespace>to avoid accidental actions on unintended clusters. - Dry Runs: Utilize
--dry-run=client -o yamlbefore applying changes in production to preview the impact.