Skip to content
TrustedSkillsbeta
Back to all skills

Kubernetes Health

Checked
nodnarbnitram·vlatest·cloud·MIT

Monitors Kubernetes cluster health, identifying resource constraints, node issues, and pod failures for proactive remediation.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add nodnarbnitram/claude-code-extensions --skill kubernetes-health -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

nodnarbnitram

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned nodnarbnitram/claude-code-extensions at 35e7f7deae.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
35e7f7deae
Manifest
.claude/skills/kubernetes-health/SKILL.md
Scanned
16 files, 2,798 lines
Copies in repo
2 — all of them scanned
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill enables AI agents to query the health status of Kubernetes clusters and inspect specific resources for operational issues. It allows agents to verify cluster readiness, check pod states, and identify potential failures within the container orchestration environment.

When to use it

  • Diagnosing why a deployment has failed or pods are stuck in CrashLoopBackOff.
  • Verifying that critical infrastructure services are running after a cluster update or restart.
  • Automating health checks before triggering automated rollback procedures.
  • Investigating resource constraints like OOMKilled errors or Pending states.

Key capabilities

  • Retrieves overall Kubernetes cluster health metrics.
  • Inspects the status of specific pods, nodes, and services.
  • Identifies common failure states such as NotReady, CrashLoopBackOff, and ImagePullBackOff.
  • Provides actionable insights into resource utilization and scheduling issues.

Example prompts

  • "Check the health of the production Kubernetes cluster and list any nodes that are not ready."
  • "Investigate why the 'payment-service' pods are failing to start and report the specific error messages."
  • "Run a diagnostic on the current cluster state and summarize any critical issues found in the last hour."

Tips & gotchas

Ensure your AI agent has appropriate RBAC permissions to read cluster resources, as health checks require access to node and pod details. This skill is most effective when combined with other Kubernetes skills that allow for remediation actions once an issue is identified.