k8s-workload-inventory

Lists Kubernetes pods, namespaces, and events with phase and readiness status.

650|182|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/automateyournetwork/netclaw --skill k8s-workload-inventory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: k8s-workload-inventory
Source: https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/k8s-workload-inventory
Command: npx skills add https://github.com/automateyournetwork/netclaw --skill k8s-workload-inventory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Operators need a fast, accurate answer to "what is running in my cluster and what is failing" without manually chaining kubectl commands, and without misreading partial results as cluster-wide truth.

Core Features & Use Cases

  • Pod Inventory: Lists pods cluster-wide or per namespace with node, phase, and readiness, always stating which scope and which cluster answered.
  • Failure Reporting: Surfaces non-running pods with their phase and reason (CrashLoopBackOff, ImagePullBackOff, Pending, Evicted) instead of hiding them in a healthy summary.
  • Event Context: Pulls namespace events to explain why a pod is failing, while flagging when events have aged out of the retention window.
  • Use Case: Ask what is failing in the production cluster and receive a scoped report distinguishing Running-but-not-Ready pods from genuinely healthy workloads.

Quick Start

Ask the agent to list all pods in the production namespace and report any that are not Ready, including recent events.

Frequently Asked Questions about k8s-workload-inventory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I list all pods in a Kubernetes cluster with their status?

Use the pods_list tool for a cluster-wide view or pods_list_in_namespace for a single namespace. Each result includes the node, phase, and readiness, and the report always states which scope and cluster answered.

How to find failing pods in a Kubernetes namespace?

List pods in the namespace and filter for phases other than Running, such as CrashLoopBackOff, ImagePullBackOff, Pending, or Evicted. Then check events_list to see the reason behind each failure.

Why does a Running pod still not serve traffic in Kubernetes?

A pod can be Running but not Ready when its readiness probe is failing, meaning it receives no traffic. Always check both phase and readiness rather than summarizing pods as healthy on phase alone.

Why does events_list return no events for a known pod problem?

Kubernetes events are time-limited, typically retained for about one hour. An empty event list for an old issue means the events aged out of the retention window, not that nothing happened.

Can this skill restart pods or change Kubernetes resources?

No. The skill is strictly read-only through the k8s-mcp server, and Secrets access is denied. For metrics use Prometheus or Grafana, and for traffic inspection use Kubeshark.