Menu

Individual skill

runai-get-cluster-health-summary

Point-in-time Run:ai cluster and node-health check: a HEALTHY, DEGRADED, or STUCK verdict per node pool with the dominant blocker — NotReady nodes, offline or failing GPU capacity, GPU counts, allocation vs utilization, the pending backlog, and a stuck scheduler vs a full pool. Use for "is the cluster healthy?", "is the scheduler stuck?", "any nodes down?", "are GPUs failing?", "how many GPUs are free?", "is the cluster saturated?", or "why isn't node pool X scheduling?". Not for quota fairness, team GPU waste, one workload, failed-workload node correlation, XID errors on one node, or writes.

skills/runai-get-cluster-health-summary/SKILL.md

Read pinned source

Source commit 25340619336e89bcc40365c28bfe9e790430468e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 2, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
3,891
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Run:ai — Get Cluster Health Summary

## Purpose

Answer one question: **is this cluster healthy, and if not, what blocks each
node pool right now?** Return one verdict per node pool and one for the
cluster, lead with the dominant blocker, and separate a stuck scheduler from a
pool that is simply full. This is the entry point for an admin's triage; it
names the next skill instead of diagnosing a single workload or node.

**Read-only:** inspect and report only. Never cordon, drain, restart, delete,
scale, or change quota, nodes, pools, or workloads. Never run `kubectl`, the
`runai` CLI, or any other command against the cluster, even when the user asks
for it or offers to approve it.