alirezarezvani/claude-skills / engineering/skills/cloud-finops
cloud-finops
VerifiedUse for any cloud cost question on AWS, Azure or Google Cloud - a bill that jumped or one service that spiked (NAT gateway, egress, storage), cost anomaly alert thresholds, untagged or unallocated spend and tag cleanup for showback or chargeback, Savings Plans, Reserved Instances or committed use discounts (utilization, coverage, unused commitment, effective savings rate, whether to buy more), or whether cost per order or per customer got worse. Reads a FOCUS billing export with stdlib scripts.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.2 KB |
| assets/finops_review_template.md | markdown | 913 B |
| assets/focus_export.example.csv | other | 10.6 KB |
| references/anomalies_and_unit_economics.md | markdown | 3.1 KB |
| references/commitments_and_esr.md | markdown | 3.1 KB |
| references/focus_and_allocation.md | markdown | 3.5 KB |
| scripts/allocation_check.py | script | 7.2 KB |
| scripts/commitment_check.py | script | 8.2 KB |
| scripts/cost_anomaly.py | script | 7.7 KB |
| scripts/focus_common.py | script | 4.8 KB |
references/commitments_and_esr.md
View on GitHub# Commitments, coverage and the effective savings rate
Verified 2026-11-17. π’ read on the primary page this session, π‘ primary not re-read, π΄ convention.
## Definitions the script uses
- π’ **Coverage:** "the percentage of eligible workloads that were covered by active commitments during the specified period". [1]
- π’ **Utilization:** "the percentage of active commitments utilized during the specified period". [1]
- π’ **Effective savings rate (ESR)** = savings / on-demand equivalent (ODE) spend; equivalently utilization Γ coverage Γ discount. The Foundation's worked example: 90% Γ 100% Γ 50% = 45%. [1]
FOCUS makes these computable: usage covered by a commitment has `CommitmentDiscountStatus = Used` and `PricingCategory = Committed`; capacity nobody used appears as `Unused` rows whose EffectiveCost is the waste. [2]
Formulas in `commitment_check.py`:
```
utilization = EffectiveCost(Used) / EffectiveCost(Used + Unused)
coverage = ListCost(Used, eligible) / ListCost(eligible usage)
ESR = (ListCost(eligible) - EffectiveCost(eligible) - EffectiveCost(Unused)) / ListCost(eligible)
```
Coverage uses ListCost because a covered hour is cheaper: measuring coverage in EffectiveCost understates it by the discount. ListCost equals the on-demand price for AWS, Azure and Google public pricing; for negotiated-rate accounts it is an approximation (π‘). ESR counts unused commitment as negative savings, which is the point: a 72% discount at 60% utilization can save less than a 40% discount at 100%.
## Decisions the numbers drive
1. **Utilization first.** Under-used commitments are sunk cost; buying more while one sits at 80% compounds the waste. The script reports `BUY_WHILE_WASTING` rather than a coverage gap in that case.
2. **Size to the floor.** The lowest daily uncovered eligible spend over the window is what a new commitment would cover every day. Above it you are betting on growth, which may be right, but say so. π΄ (standard practice; see [3][4])
3. **Prefer flexible instruments when the floor moves.** Compute Savings Plans cover instance family, Region and some serverless; EC2 Instance Savings Plans and Standard RIs discount more but bind more. π‘ [4][5]
4. **Commitment terms outlive architecture.** A 3-year term on a workload you plan to move to containers or ARM is a migration tax. π΄
## Sources
1. FinOps Foundation working group, "How to Calculate Effective Savings Rate (ESR)", finops.org/wg/how-to-calculate-effective-savings-rate-esr/
2. FinOps Foundation, FOCUS v1.4 Appendix 8.2 "Examples: Commitment Discounts", focus.finops.org/docs/specification/v1-4/sections/appendix/commitment-discounts/
3. FinOps Foundation, "Rate Optimization" FinOps Framework capability, finops.org/framework/capabilities/rate-optimization/
4. AWS, Savings Plans User Guide, "What are Savings Plans?", docs.aws.amazon.com/savingsplans/latest/userguide/what-is-savings-plans.html
5. Google Cloud, "Committed use discounts", cloud.google.com/docs/cuds
6. Microsoft Learn, "What are Azure savings plans for compute?", learn.microsoft.com/azure/cost-management-billing/savings-plan/savings-plan-compute-overview
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |