How do I install the Kubernetes skill?

Run npx skillmds@latest add tomevault-io/kubernetes-11 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Kubernetes safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Kubernetes?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Kubernetes free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Kubernetes?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Kubernetes by tomevault-io — Agent Skill

Name: Kubernetes
Author: tomevault-io

File contents

Kubernetes Operations Guide

When to Use This Skill

Use when managing Kubernetes deployments, troubleshooting pod issues, viewing application logs, scaling services, or debugging container problems.

Common Operations

View Resources

kubectl get pods -n <namespace>
kubectl get pods -n <namespace> -o wide
kubectl get pods -n <namespace> -l app=<app-name>
kubectl get deployments -n <namespace>
kubectl get svc -n <namespace>
kubectl get ingress -n <namespace>
kubectl get all -n <namespace>

Logs

kubectl logs -n <namespace> <pod-name>
kubectl logs -n <namespace> <pod-name> -f
kubectl logs -n <namespace> <pod-name> --tail=100
kubectl logs -n <namespace> <pod-name> --previous
kubectl logs -n <namespace> -l app=<app-name> --all-containers=true
kubectl logs -n <namespace> <pod-name> --since=1h

Describe & Debug

kubectl describe pod -n <namespace> <pod-name>
kubectl describe deployment -n <namespace> <deployment>
kubectl get events -n <namespace> --sort-by='.lastTimestamp'
kubectl top pods -n <namespace>
kubectl top nodes

Execute Commands

kubectl exec -it -n <namespace> <pod-name> -- /bin/sh
kubectl exec -n <namespace> <pod-name> -- cat /app/config.json
kubectl port-forward -n <namespace> svc/<service> <local-port>:<remote-port>

Scaling

kubectl scale deployment -n <namespace> <deployment> --replicas=<n>
kubectl get hpa -n <namespace>
kubectl describe hpa -n <namespace> <hpa-name>

Rollouts

kubectl rollout restart deployment -n <namespace> <deployment>
kubectl rollout status deployment -n <namespace> <deployment>
kubectl rollout history deployment -n <namespace> <deployment>
kubectl rollout undo deployment -n <namespace> <deployment>

Troubleshooting

Pod in CrashLoopBackOff

Check logs from previous container: kubectl logs -n <ns> <pod> --previous
Check events: kubectl describe pod -n <ns> <pod>
Common causes: missing env vars, secret not synced, DB connection failed, OOMKilled

Pod in Pending

Check events: kubectl describe pod -n <ns> <pod>
Check node resources: kubectl top nodes
Common causes: insufficient CPU/memory, node selector mismatch, PVC not bound

Pod in ImagePullBackOff

Verify image exists: kubectl describe pod -n <ns> <pod> | grep -A5 "Image:"
Check registry authentication

Service Not Responding

Verify pods are running: kubectl get pods -n <ns> -l app=<app>
Check endpoints: kubectl get endpoints -n <ns> <service>
Test connectivity: kubectl run debug --rm -it --image=busybox -- wget -qO- http://<svc>.<ns>.svc.cluster.local

Best Practices

Always verify context before running commands
Use labels for filtering resources
Check events first when troubleshooting
Don't delete pods without understanding the impact
Use rollout restart instead of deleting pods
Scale gradually — don't jump from 2 to 20 replicas

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: kubernetes-11description: Kubernetes/EKS patterns. Use when managing deployments, pods, troubleshooting containers, viewing logs, or scaling applications. Use when this capability is needed.---# Kubernetes Operations Guide## When to Use This SkillUse when managing Kubernetes deployments, troubleshooting pod issues, viewing application logs, scaling services, or debugging container problems.## Common Operations### View Resources```bashkubectl get pods -n <namespace>kubectl get pods -n <namespace> -o widekubectl get pods -n <namespace> -l app=<app-name>kubectl get deployments -n <namespace>kubectl get svc -n <namespace>kubectl get ingress -n <namespace>kubectl get all -n <namespace>```### Logs```bashkubectl logs -n <namespace> <pod-name>kubectl logs -n <namespace> <pod-name> -fkubectl logs -n <namespace> <pod-name> --tail=100kubectl logs -n <namespace> <pod-name> --previouskubectl logs -n <namespace> -l app=<app-name> --all-containers=truekubectl logs -n <namespace> <pod-name> --since=1h```### Describe & Debug```bashkubectl describe pod -n <namespace> <pod-name>kubectl describe deployment -n <namespace> <deployment>kubectl get events -n <namespace> --sort-by='.lastTimestamp'kubectl top pods -n <namespace>kubectl top nodes```### Execute Commands```bashkubectl exec -it -n <namespace> <pod-name> -- /bin/shkubectl exec -n <namespace> <pod-name> -- cat /app/config.jsonkubectl port-forward -n <namespace> svc/<service> <local-port>:<remote-port>```### Scaling```bashkubectl scale deployment -n <namespace> <deployment> --replicas=<n>kubectl get hpa -n <namespace>kubectl describe hpa -n <namespace> <hpa-name>```### Rollouts```bashkubectl rollout restart deployment -n <namespace> <deployment>kubectl rollout status deployment -n <namespace> <deployment>kubectl rollout history deployment -n <namespace> <deployment>kubectl rollout undo deployment -n <namespace> <deployment>```## Troubleshooting### Pod in CrashLoopBackOff1. Check logs from previous container: `kubectl logs -n <ns> <pod> --previous`2. Check events: `kubectl describe pod -n <ns> <pod>`3. Common causes: missing env vars, secret not synced, DB connection failed, OOMKilled### Pod in Pending1. Check events: `kubectl describe pod -n <ns> <pod>`2. Check node resources: `kubectl top nodes`3. Common causes: insufficient CPU/memory, node selector mismatch, PVC not bound### Pod in ImagePullBackOff1. Verify image exists: `kubectl describe pod -n <ns> <pod> | grep -A5 "Image:"`2. Check registry authentication### Service Not Responding1. Verify pods are running: `kubectl get pods -n <ns> -l app=<app>`2. Check endpoints: `kubectl get endpoints -n <ns> <service>`3. Test connectivity: `kubectl run debug --rm -it --image=busybox -- wget -qO- http://<svc>.<ns>.svc.cluster.local`## Best Practices1. Always verify context before running commands2. Use labels for filtering resources3. Check events first when troubleshooting4. Don't delete pods without understanding the impact5. Use `rollout restart` instead of deleting pods6. Scale gradually — don't jump from 2 to 20 replicas---> Converted and distributed by [TomeVault](https://tomevault.io/claim/arvoreeducacao) — claim your Tome and manage your conversions.

Frequently asked questions

Kubernetes