Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →notque/kubernetes
Kubernetes operations: debugging, security, RBAC, and infrastructure tooling.
Passed 19 of 22 test cases with the skill, and 13 of 22 without it.
and 4 more in the full report
6 fixed13 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need to temporarily connect my local laptop port 8080 to an internal web service `grafana-dashboard` on port 80 in namespace `monitoring`. Provide the exact `kubectl` command line for this.
| Checked | Without skill | With skill |
|---|---|---|
| Includes kubectl port-forward svc/grafana-dashboard -n monitoring 8080:80 | Missed | Passed |
The instructions your model reads when the skill loads.
Three domains: debugging (pod triage, networking, resources), security (RBAC, pod hardening, network isolation, supply chain), and cobaltcore (KVM exporter, hypervisor metrics). Select by request signal, then follow the phases below.
Always specify -n <namespace> in every kubectl command. Use read-only commands to gather evidence before proposing changes.
| Signal | Domain |
|---|---|
| CrashLoopBackOff, OOMKilled, ImagePullBackOff, Pending | Debugging |
| Service unreachable, DNS failure, port-forward | Debugging (network) |
| CPU throttling, memory limit, disk pressure | Debugging (resources) |
| RBAC, permissions, roles, ServiceAccount | Security (access) |
| Pod hardening, container security, PodSecurity | Security (pods) |
| NetworkPolicy, default-deny, namespace isolation | Security (network) |
| Image signing, secrets, admission control | Security (supply chain) |
| KVM exporter, cobaltcore, hypervisor metrics | Cobaltcore |
Follow this sequence for every pod or workload issue. Do not skip steps -- many failures are only visible in events and describe output, not in logs.
kubectl get pods -n <namespace> -o wide
kubectl describe pod <pod-name> -n <namespace>
kubectl logs <pod-name> -n <namespace> -c <container-name>
kubectl logs <pod-name> -n <namespace> -c <container-name> --previous
kubectl get events -n <namespace> --sort-by='.lastTimestamp'
kubectl exec -it <pod-name> -n <namespace> -c <container-name> -- /bin/sh
Always check --previous logs for crashed containers before current logs -- restarting destroys them permanently.
test cases passed, vs 13 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.