What problem does it solve? Kubernetes teams cannot answer "what did this workload cost, and where did that number come from?" without a working measurement plane. This Skill guides the full OpenCost lifecycle — deployment, Prometheus wiring, cloud billing integration, API querying, exports, and troubleshooting — so every cost figure is qualified by its pricing source, window, and idle treatment instead of being an unlabeled guess. ## Core Features & Use Cases - Deployment & Prometheus wiring: Install OpenCost via Helm, raw manifest, Docker, or exporter-only chart, configure the mandatory job_name: opencost scrape target, and set up multi-cluster identity against Thanos/Cortex/Mimir. - Pricing configuration: Wire AWS Athena/CUR, Azure RateCard, GCP BigQuery billing export, or custom on-prem pricing through cloud-integration.json with least-privilege, read-only credentials (IRSA, GKE Workload Identity). - Querying, exports & troubleshooting: Query /allocation, /assets, /cloudCost, and /customCost/* with correct window/aggregate/resolution/idle semantics, export to CSV/Parquet, use the MCP server, and diagnose empty data, 500s, and negative idle. - Use Case: A platform engineer notices the allocation API returns empty data. The Skill directs them to verify the Prometheus scrape target first, run the read-only health and pricing-check scripts, and confirm whether numbers reflect list pricing or a real cloud billing integration. ## Quick Start Ask the agent to install OpenCost into the opencost namespace with Helm, wire the Prometheus scrape config, and verify the deployment answers /allocation/compute with non-empty data.