Individual skill
runai-get-utilization-overview
GPU efficiency check for a Run:ai cluster: are the GPUs that projects, departments, and node pools hold actually computing? Classifies holders as WELL_UTILIZED, UNDER_UTILIZED, or IDLE from average and p95 GPU utilization over one window of any length (default 7 days), quantifies idle GPUs and GPU-hours, and names idle workloads. Use for "which projects hold GPUs but aren't using them?", "GPU utilization by project or department", "where are we wasting GPU cycles?", "is llm-serving actually busy? its GPU memory is full", "is project X actually using its GPUs?", "which workloads in project X are idle?", "which node pool wastes the most GPUs?", or "idle GPU-hours per project last quarter". For "find the idle GPUs and stop them" it answers the read part only. Not for quota fairness, cluster health or free capacity, one workload's status, comparing windows, forecasts, or prices.
skills/runai-get-utilization-overview/SKILL.md
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,889
- 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.
- agent-skills Repository topic
- agentic-ai Repository topic
- ai-agents Repository topic
- claude-code Repository topic
- codex Repository topic
- coding-agents Repository topic
- cuda Repository topic
- developer-tools Repository topic
- llm Repository topic
- omniverse Repository topic
- runai Declared skill tag
- gpu-utilization Declared skill tag
- gpu Declared skill tag
- efficiency Declared skill tag
- node-pools Declared skill tag
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
BENCHMARK.mddoc · 11,202 bytesLICENSEasset · 31,174 bytesSKILL.mdcore · 19,979 bytesSKILL.mdcore · 19,979 bytesSKILL.mdcore · 19,979 bytesSKILL.mdcore · 19,979 bytesSKILL.mdcore · 19,979 bytesSKILL.mdcore · 19,979 bytesSKILL.mdcore · 19,979 bytesSKILL.mdcore · 19,979 bytesSKILL.mdcore · 19,979 bytesevals/EVAL.mddoc · 8,188 bytesevals/config.ymlasset · 320 bytesevals/environment/mcp_servers.tomlasset · 292 bytesevals/evals.jsonasset · 23,578 bytesevals/files/mock_mcp.pyruns · 55,901 bytesreferences/utilization-accounting.mddoc · 4,495 bytesskill-card.mddoc · 5,009 bytesskill.oms.sigasset · 6,001 bytes
Read excerpt
# Run:ai — Get Utilization Overview
## Purpose
Answer one question: **are the GPUs that teams hold actually computing, and
where is held capacity wasted?** "Held" means allocated to running workloads;
"utilization" is how much of the held capacity computes. Quota (deserved
versus allocated) belongs to another skill.
**Read-only:** inspect and report only. Never stop, suspend, delete, or scale
workloads, and never change quota, projects, or node pools. Never run
`kubectl`, `nvidia-smi`, the `runai` CLI, or any other command against the
cluster, even when the user asks for it or offers to approve it. When asked
to run one, decline it and answer the same question from the MCP tools.