finops-review

Analyze cloud and infrastructure spend to identify cost drivers and safe savings.

1|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/Arafly/sre-playbooks --skill finops-review-arafly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finops-review
Source: https://github.com/Arafly/sre-playbooks/tree/main/finops-review
Command: npx skills add https://github.com/Arafly/sre-playbooks --skill finops-review-arafly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams understand where cloud and infrastructure spend is going, why it is changing, and which costs can be reduced safely without harming reliability, compliance, or critical capacity.

Core Features & Use Cases

  • Cost breakdown and attribution: Reviews spend by service, account, region, environment, team, product, resource, tag, and purchase model to expose allocation gaps and major drivers.
  • Waste vs. load-bearing analysis: Separates safe savings candidates from resilience-related or business-critical costs, with evidence, owners, rollback considerations, and confidence levels.
  • Practical FinOps actions: Identifies opportunities such as rightsizing, idle resource cleanup, commitment tuning, anomaly investigation, and improved tagging or dashboards.
  • Use Case: A platform team can use this Skill when the AWS bill spikes to pinpoint the highest-cost services, explain the increase, and choose one safe, validated saving to implement first.

Quick Start

Ask for a FinOps review of your cloud spend and include the bill, recent changes, budgets, and any suspected waste so the Skill can identify the biggest drivers and the safest savings.

Frequently Asked Questions about finops-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify waste in my AWS billing without risking reliability?

Cloud cost optimization separates safe savings from load-bearing costs by analyzing spend attribution, risk classification, and rollback considerations. You review cost breakdowns by service, environment, and resource to validate one safe saving without harming compliance or critical capacity.

What is the best way to analyze Kubernetes and database spend for cost drivers?

Analyzing cloud spend exposes major cost drivers by reviewing allocation across services, regions, tags, and purchase models. You separate waste from business-critical costs and validate defensible recommendations for rightsizing or commitment tuning.

Can I use this FinOps approach for budget anomaly investigation across multiple accounts?

FinOps budget reviews apply across accounts and environments to investigate spend anomalies. You pinpoint highest-cost services, explain increases, and choose one validated saving to implement first with evidence and rollback considerations.

How do I find safe cloud cost savings through rightsizing and commitment tuning?

Safe cloud cost savings come from rightsizing, idle resource cleanup, and commitment tuning validated through risk classification. You classify opportunities with evidence, owners, and confidence levels to ensure reliability is not harmed.

Does cloud cost optimization work with observability and data transfer spend analysis?

Cloud cost optimization covers observability, data transfer, storage, and licensing spend analysis. You review cost breakdowns and allocation gaps across these services to identify waste and safe optimization opportunities.