Kubernetes Operations
CheckedAutomate Kubernetes deployments, scaling, troubleshooting, and resource management tasks via laurigates's specialized AI agent.
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 laurigates/claude-plugins --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
laurigates
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 laurigates/claude-plugins at 45d1d7dcf6.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 45d1d7dcf6
- Scanned
- 1 file, 159 lines
About this skill
What it does
This skill enables AI agents to automate and manage Kubernetes clusters, deployments, and troubleshoot issues using kubectl commands and cloud-native best practices. It provides expertise in workload management (Deployments, StatefulSets, etc.), networking (Services, Ingress), configuration & storage (ConfigMaps, PersistentVolumes), and debugging. The agent will prioritize declarative YAML manifests for resource management and emphasizes validation and verification after applying changes.
When to use it
- You need to deploy new applications or update existing deployments within a Kubernetes cluster.
- You are experiencing issues with pod crashes (
CrashLoopBackOff) or other application errors and require assistance in debugging. - You want to monitor the health of your nodes, pods, and services within a Kubernetes environment.
- You need to inspect resource usage (CPU, memory) for pods and nodes.
- You're performing routine cluster maintenance tasks like cleanup of unused resources.
Key capabilities
- Workload Management: Deploying, updating, and managing various Kubernetes workloads including Deployments, StatefulSets, DaemonSets, Jobs, and CronJobs.
- Networking Configuration: Managing Services, Ingress, NetworkPolicies, and DNS configurations within the cluster.
- Configuration & Storage: Handling ConfigMaps, Secrets, PersistentVolumes, and PersistentVolumeClaims.
- Troubleshooting: Debugging pods, analyzing logs, inspecting cluster events, and identifying common issues like
CrashLoopBackOff. - Manifest-First Approach: Prioritizing declarative YAML manifests for resource management.
- Validation & Verification: Utilizing
--dry-runflags and inspection commands (kubectl get,kubectl describe) to ensure changes are valid and successful.
Example prompts
- "Deploy the application defined in
my-app.yaml." - "What is causing this pod named 'webserver' to crash?"
- "Show me the logs for the previous instance of the 'database' pod."
- "Check the status of the deployment named 'frontend'."
Tips & gotchas
- Context Safety: Always explicitly specify the Kubernetes context using
--context=<context-name>in every command to avoid unintended operations on different clusters. This is critical for preventing accidental changes. - Manifests are Key: The agent prioritizes declarative YAML manifests; ensure your resources are defined this way.
- Validation is Important: Use the
--dry-run=clientflag before applying any changes to validate them and prevent errors.