Install any skill in seconds. Free to start, no credit card required.
Get Started Free →bregman-arie/Triage Pending Pods
Diagnose pods stuck in Pending and identify scheduling constraints.
Passed 22 of 22 test cases with the skill, and 18 of 22 without it.
and 1 more in the full report
4 fixed18 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
Which specific `kubectl` command inspects a pending pod's event history within the `backend` namespace for pod `api-6f9d`?
| Checked | Without skill | With skill |
|---|---|---|
| The response includes `kubectl -n backend describe pod api-6f9d`. | Missed | Passed |
The instructions your model reads when the skill loads.
Use when pods remain in Pending longer than expected.
Insufficient cpu/memory: scale cluster, reduce requests, or shed load.taint {node.kubernetes.io/...}: add toleration only if correct.pod affinity/anti-affinity: loosen rules if they are too strict.unbound immediate PersistentVolumeClaims: investigate storage class/provisioner.exceeded quota: adjust quota or reduce consumption.Pending to Running.test cases passed, vs 18 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.