Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From claude-devops
Investigate Kubernetes/EKS issues by running run-investigation.sh with the issue type, resource name, kubectl context, and namespace.
npx claudepluginhub kjenney/claude-devopsHow this skill is triggered — by the user, by Claude, or both
Slash command
/claude-devops:eks-troubleshootingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The `/eks-investigate` command and `eks-investigator` agent run the automated investigation orchestrator:
Diagnoses and fixes Kubernetes pod failures like CrashLoopBackOff, Pending, DNS, networking, storage mounts, and rollout issues using kubectl workflows and scripts.
Reviews Amazon EKS Kubernetes platform operations: cluster access, IRSA, pod identity, node groups, Karpenter, autoscaling, network policy, upgrades, reliability, observability, and cost. Activates automatically on EKS/Kubernetes topics.
Assists with Kubernetes kubectl operations: debugging (logs, describe, exec, port-forward), managing resources (deployments, services, configmaps, secrets), and cluster tasks (scaling, rollouts, nodes). Use for pods, services, or troubleshooting.
Share bugs, ideas, or general feedback.
The /eks-investigate command and eks-investigator agent run the automated investigation orchestrator:
bash skills/eks-troubleshooting/run-investigation.sh "<issue-type>" "<resource-name>" "<context>" "<namespace>"
deployment - Pod status, rollout status, events, restart counts, resource usagenetworking - Service details, endpoints, DNS resolution, network policiesnode - Node status, conditions, resource pressure, taints/tolerationsingress - Ingress configuration, backend services, certificate status/eks-investigate commandexamples/investigate-deployment.sh - Queries deployment status, events, pod logsexamples/investigate-networking.sh - Queries service endpoints, DNS, network policies