Agent skill · Data & Analytics

coreweave-gpu-cost-leak-hunter

Hunt down CoreWeave GPU cost leaks — idle reserved capacity, wrong-GPU-type right-sizing waste, allocated-but-idle instances, and on-demand spend that should be committed — then produce a CFO-grokkable, dollar-ranked FinOps report. CoreWeave ships no cost dashboard and no billing API, so the spend view is built from PromQL against its managed Grafana. Use when a user asks why their CoreWeave GPU bill is high, wants to find wasted GPU spend or idle reservations, or needs a GPU FinOps cost report. Trigger with "coreweave cost", "why is my coreweave bill", "wasted GPU spend", "idle reserved cap

jeremylongshoregithub.com/jeremylongshoreGitHub ↗
claude-codecan modify filesships scriptsMIT
Install
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill coreweave-gpu-cost-leak-hunter --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 9
SKILL.md size: 14 KB
Bundled scripts: yes
Version: 1.11.0
Declared author: Jeremy Longshore <jeremy@intentsolutions.io>
Allowed tools: ReadWriteEditGlobBash(curl:*)Bash(jq:*)Bash(kubectlget:*)Bash(python3:*)
Requires: Designed for Claude Code, also compatible with Codex
Path: skills/.curated/coreweave-gpu-cost-leak-hunter/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,596
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# CoreWeave GPU Cost Leak Hunter > **Community-contributed.** Not affiliated with, endorsed by, or sponsored by > CoreWeave, Inc. CoreWeave is a registered trademark of CoreWeave, Inc. Audits a CoreWeave GPU cluster for real-dollar cost leaks — idle reserved capacity, GPUs on the wrong SKU, allocated-but-idle instances, and steady on-demand spend that should be committed — then emits a CFO-grokkab

More from claude-code-plugins-plus-skills
All skills →
building-automl-pipelinesBuild automated machine learning pipelines with feature engineering, model selection, and…Data & Analyticsprocessing-computer-vision-tasksProcess images using object detection, classification, and segmentation. Use when requesting…AI & Agentsvalidating-ai-ethics-and-fairnessValidate AI/ML models and datasets for bias, fairness, and ethical concerns. Use when auditing AI…AI & Agentsorchestrating-multi-agent-systemsExecute orchestrate multi-agent systems with handoffs, routing, and workflows across AI providers.…Workflow & Productivityrunning-clustering-algorithmsAnalyze datasets by running clustering algorithms (K-means, DBSCAN, hierarchical) to identify data…Data & Analyticspreprocessing-data-with-automated-pipelinesProcess automate data cleaning, transformation, and validation for ML tasks. Use when requesting…Data & Analytics
About this skill
What does the coreweave-gpu-cost-leak-hunter skill do?

Hunt down CoreWeave GPU cost leaks — idle reserved capacity, wrong-GPU-type right-sizing waste, allocated-but-idle instances, and on-demand spend that should be committed — then produce a CFO-grokkable, dollar-ranked FinOps report. CoreWeave ships no cost dashboard and no billing API, so the spend view is built from PromQL against its managed Grafana. Use when a user asks why their CoreWeave GPU bill is high, wants to find wasted GPU spend or idle reservations, or needs a GPU FinOps cost report. Trigger with "coreweave cost", "why is my coreweave bill", "wasted GPU spend", "idle reserved cap

How do I install it?

Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill coreweave-gpu-cost-leak-hunter --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.