How do I install the Infra Pods skill?

Run npx skillmds@latest add weorbitant/infra-pods in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Infra Pods safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Infra Pods?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Infra Pods free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Infra Pods?

weorbitant (@weorbitant) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Infra Pods by weorbitant — Agent Skill

Name: Infra Pods
Author: weorbitant

Infra Pods

Use when checking pod status, listing running services, investigating crashloops, viewing pod events, or checking resource usage. Use when user says "pods", "qué está corriendo", "pod status", "check pods", "restart", "crashloop", or "pod events".

weorbitant 29ffbb7 2.8 KB Updated Sep 17, 2026

File contents

Kubernetes Pod Management

Overview

Inspect pod status, health, events, and resource usage across cluster environments.

Pod Status

List pods for a service

kubectl --context=<env> get pods -n <namespace> | grep <service>

List all pods in a namespace with status

kubectl --context=<env> get pods -n <namespace> -o wide

Check for unhealthy pods

kubectl --context=<env> get pods -n <namespace> | grep -v "Running\|Completed"

Diagnostics

Pod details and events

kubectl --context=<env> describe pod <pod> -n <namespace> | tail -30

Events show recent scheduling, pulling, starting, and crash info.

Check restart counts

kubectl --context=<env> get pods -n <namespace> -o custom-columns=\
NAME:.metadata.name,STATUS:.status.phase,RESTARTS:.status.containerStatuses[0].restartCount,\
AGE:.metadata.creationTimestamp | grep <service>

Pod resource usage

kubectl --context=<env> top pods -n <namespace> | grep <service>

Environment variables (non-secret)

kubectl --context=<env> exec -n <namespace> <pod> -- env | grep -iv "pass\|secret\|token\|key" | sort

Check which image/version is running

kubectl --context=<env> get pod <pod> -n <namespace> \
  -o jsonpath='{.spec.containers[0].image}'

The image tag is the GitHub Actions run ID (databaseId). To find which PR/commit it corresponds to:

# Cross-reference image tag with CI runs on main
gh run list --repo <org>/<repo> --branch main --json databaseId,displayTitle,headSha \
  | jq '.[] | select(.databaseId == <image-tag>)'

Common Namespaces

Read namespace names from the project's CLAUDE.md (## Infrastructure section). Typical patterns:

Application services: one namespace per cluster (e.g. plataformadato)
Shared infrastructure (RabbitMQ, monitoring): separate namespace (e.g. shared-infra)

Rollout Management

Check deployment status

kubectl --context=<env> get deploy -n <namespace> | grep <service>

Restart a deployment (rolling)

⚠️ ALWAYS ask for explicit confirmation before running this command, in any environment. State clearly: what deployment will restart, in which environment, and what the impact is (brief downtime during rollout). Do NOT run without the user saying "yes", "proceed", or equivalent.

kubectl --context=<env> rollout restart deployment/<deployment> -n <namespace>

Check rollout history

kubectl --context=<env> rollout history deployment/<deployment> -n <namespace>

---name: infra-podsdescription: Use when checking pod status, listing running services, investigating crashloops, viewing pod events, or checking resource usage. Use when user says "pods", "qué está corriendo", "pod status", "check pods", "restart", "crashloop", or "pod events".---# Kubernetes Pod Management## OverviewInspect pod status, health, events, and resource usage across cluster environments.## Pod Status### List pods for a service```bashkubectl --context=<env> get pods -n <namespace> | grep <service>```### List all pods in a namespace with status```bashkubectl --context=<env> get pods -n <namespace> -o wide```### Check for unhealthy pods```bashkubectl --context=<env> get pods -n <namespace> | grep -v "Running\|Completed"```## Diagnostics### Pod details and events```bashkubectl --context=<env> describe pod <pod> -n <namespace> | tail -30```Events show recent scheduling, pulling, starting, and crash info.### Check restart counts```bashkubectl --context=<env> get pods -n <namespace> -o custom-columns=\NAME:.metadata.name,STATUS:.status.phase,RESTARTS:.status.containerStatuses[0].restartCount,\AGE:.metadata.creationTimestamp | grep <service>```### Pod resource usage```bashkubectl --context=<env> top pods -n <namespace> | grep <service>```### Environment variables (non-secret)```bashkubectl --context=<env> exec -n <namespace> <pod> -- env | grep -iv "pass\|secret\|token\|key" | sort```### Check which image/version is running```bashkubectl --context=<env> get pod <pod> -n <namespace> \ -o jsonpath='{.spec.containers[0].image}'```The image tag is the **GitHub Actions run ID** (`databaseId`). To find which PR/commit it corresponds to:```bash# Cross-reference image tag with CI runs on maingh run list --repo <org>/<repo> --branch main --json databaseId,displayTitle,headSha \ | jq '.[] | select(.databaseId == <image-tag>)'```## Common NamespacesRead namespace names from the project's CLAUDE.md (`## Infrastructure` section). Typical patterns:- Application services: one namespace per cluster (e.g. `plataformadato`)- Shared infrastructure (RabbitMQ, monitoring): separate namespace (e.g. `shared-infra`)## Rollout Management### Check deployment status```bashkubectl --context=<env> get deploy -n <namespace> | grep <service>```### Restart a deployment (rolling)> ⚠️ **ALWAYS ask for explicit confirmation before running this command, in any environment.**> State clearly: what deployment will restart, in which environment, and what the impact is (brief downtime during rollout).> Do NOT run without the user saying "yes", "proceed", or equivalent.```bashkubectl --context=<env> rollout restart deployment/<deployment> -n <namespace>```### Check rollout history```bashkubectl --context=<env> rollout history deployment/<deployment> -n <namespace>```

Frequently asked questions