Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →automateyournetwork/k8s-service-path
Trace the Kubernetes service path — Service to selector to pods to EndpointSlices to readiness, plus Ingress routing.
Passed 14 of 18 test cases with the skill, and 12 of 18 without it.
and 4 more in the full report
5 fixed13 passed either way3 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
An Ingress in namespace `gateway` references a backend service without cluster-wide API permission confirmation. The scan returns no endpoints for the backend. What warning must be issued?
| Checked | Without skill | With skill |
|---|---|---|
| Warns that cross-namespace tracing without cluster-wide permission scope may be silently incomplete. | Missed | Passed |
| Refrains from declaring the path definitively healthy without scope verification. | Passed | Passed |
The instructions your model reads when the skill loads.
k8s-mcp — vendored third-party, read-only, 7 tools. See
k8s-network-policy for the shared preflight and the empty-result cautions,
which apply here identically.
Ingress → Service → selector → Pods → EndpointSlice → readiness
Mark every link checked or not checked. A partial trace presented as complete is the failure mode of this skill — "the service is fine" after checking two of five links is worse than saying nothing, because it sends the next person somewhere else.
resources_list({"apiVersion":"networking.k8s.io/v1","kind":"Ingress"})
resources_get ({"apiVersion":"v1","kind":"Service","namespace":"app1","name":"web"})
pods_list_in_namespace({"namespace":"app1"}) // then match against the Service selector
resources_list({"apiVersion":"discovery.k8s.io/v1","kind":"EndpointSlice","namespace":"app1"})
| Symptom | Actual cause | How to say it |
|---|---|---|
| No endpoints | Selector matches no pods | "The Service selector app=web matches no pods" — the selector is wrong or the pods are gone |
| No endpoints | Pods exist but none are ready | "3 pods match but none are Ready" — a readiness-probe problem, not a wiring problem |
| No endpoints | Pods ready, port mismatch | "Pods are ready but no container exposes the target port" |
| Traffic blocked | A NetworkPolicy denies it | hand off to k8s-network-policy — this skill does not evaluate policy |
| Ingress not routing | Backend names a non-existent Service | "Ingress web routes to Service web-v2, which does not exist" — call this out loudly, it is a common and silent misconfiguration |
"No endpoints" is a symptom, never a diagnosis. Always name which of these it is.
test cases passed, vs 12 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.