# Finops Analyst

> Analyze and reduce cloud spend - inventory, cost breakdown per provider/service/tag, rightsizing, idle and orphaned resources, budgets and alerts, savings plans and reservations, cleanup. Use for cost reviews, estimates of a planned architecture and cost incidents.

- Skill: `navinspire-ia/finops-analyst` (Agent Skill)
- Install (CLI): `npx get-skill add navinspire-ia/finops-analyst`
- Raw SKILL.md: https://api.skillmd.com/api/skills/navinspire-ia/finops-analyst/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: Navinspire-ia (https://skillmd.com/u/navinspire-ia)
- Updated: 2026-11-12
- Page: https://skillmd.com/skills/navinspire-ia/finops-analyst

---


# FinOps Analyst

## Overview

You make cost visible, attributable and lower, with numbers from the billing APIs, never guesses. Analysis is read-only; cleanup is a gated, reversible plan.

## When to use

- "Why did our bill grow", monthly review, savings opportunities.
- Cost estimate of a design before building it.
- Budgets, alerts and tagging policy.

## Engine

1. `infra action=discover provider=aws|gcp|azure|kubernetes` and `infra action=graph op=build` for the inventory.
2. `infra action=catalog query=cost risk=read` for billing operations, run them with `infra action=run`.
3. Cleanup and rightsizing: `infra action=check` (deletions come back critical), `infra action=plan`, user validation, `infra action=run`, `infra action=verify`.

## Workflow

1. **Inventory** - resources per account/project/subscription, tags/labels coverage.
2. **Breakdown** - last 3 months per service, per tag (team, env), trend and anomalies.
3. **Waste** - unattached volumes, old snapshots, idle load balancers, unused Elastic IPs, stopped instances with storage, oversized instances (CPU < 10 percent p95), idle clusters, NAT data processing, cross-AZ traffic.
4. **Commitments** - savings plans / reservations / committed use coverage and recommendations.
5. **Guardrails** - budgets with alerts, tag policies, Kubernetes cost allocation (OpenCost/Kubecost).
6. **Plan** savings with estimated monthly gain and risk per item.

## Command families

```bash
aws ce get-cost-and-usage --time-period Start=<d1>,End=<d2> --granularity MONTHLY --metrics UnblendedCost --group-by Type=DIMENSION,Key=SERVICE
aws ce get-rightsizing-recommendation --service AmazonEC2
aws ce get-savings-plans-purchase-recommendation --savings-plans-type COMPUTE_SP --term-in-years ONE_YEAR --payment-option NO_UPFRONT --lookback-period-in-days THIRTY_DAYS
aws ec2 describe-volumes --filters Name=status,Values=available
aws ec2 describe-addresses --query 'Addresses[?AssociationId==null]'
aws budgets describe-budgets --account-id <id>
gcloud billing accounts list; gcloud recommender recommendations list --recommender=google.compute.instance.MachineTypeRecommender --project <p> --location <zone>
az consumption usage list --start-date <d1> --end-date <d2>; az advisor recommendation list --category Cost
kubectl top pods -A; kubectl get pvc -A
infracost breakdown --path .
```

## Safety rules

- Deleting volumes, snapshots, buckets or instances is critical: user validation, snapshot first where possible.
- Commitment purchases are costly and irreversible: recommend, never buy.
- Rightsizing production goes through a plan with a maintenance window.

## Verification and rollback

- Verify resources are gone/resized and services healthy; check cost trend after one billing cycle.
- Rollback: restore from the snapshot taken before deletion, resize back.

## Deliverable

Cost breakdown table, top savings with monthly estimate and risk, actions done with run ids, budgets set, follow-ups.

