finops-analyst

Name: finops-analyst
Author: rade-nugroho

github.com/rade-nugrohoCloud & DevOps1236 installsUpdated 23w ago

About finops-analyst

A FinOps skill for teams analyzing and optimizing cloud costs, including cost management, budgeting, and allocation. It covers workflows from bill analysis and waste identification to forecasting, anomaly investigation, and unit economics reporting.

Key features

01Bill and usage analysis
02Tagging and cost allocation design
03Waste and sizing identification
04Usage commitment recommendations
05Budgets, forecasts, and anomaly analysis
06Unit economics reporting

Use cases

01Break down costs by account, service, or tag
02Find idle or over-provisioned resources
03Set budgets and explain spend variances
04Estimate cost per tenant or API

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/rade-nugroho/agentic-enteprises-skill --skill finops-analyst

After installing, type/finops-analystin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/

budgeting_forecasting.md

cost_visibility_allocation.md

finops_governance.md

finops_scope_and_principles.md

optimization_rightsizing.md

unit_economics_reporting.md

Details

From the project README

FinOps Analyst

When to Use

Analyze cloud bills and usage (CUR, Cost Explorer, billing export, Cost Management)
Design tagging and allocation keys for showback or chargeback
Find waste — idle compute, unattached storage, orphaned IPs, over-provisioned SKUs
Recommend commitments — RIs, Savings Plans, CUDs, reservations (usage-based)
Build budgets, forecasts, and variance explanations for leadership
Detect anomalies and investigate spend spikes
Report unit economics — cost per tenant, API, feature, or environment
Run FinOps reviews with service owners (monthly optimization cadence)
Model what-if scenarios (region move, architecture change, commit purchase)

When NOT to Use

Map cloud spend to GL, amortize prepaids, fixed assets → compute-accounting-manager
Enterprise agreement strategy and org-wide CCoE FinOps program → enterprise-cloud-architect
Provision VPC, fix IAM, implement infra → cloud-engineer
Execute access tickets and patch windows → cloud-system-administrator
Rack/GPU utilization and stranded kW → data-center-compute-supply-efficiency
Capex policy and board asset governance → director-infrastructure-capex-accounting
Generic BI without cloud cost domain → bi-analyst
SOC 2 cloud evidence → cloud-compliance-specialist
TCO/NPV business cases, commit portfolio economics, CFO scenarios → cloud-economist
Cloud program strategy, migration portfolio, EA sign-off → vp-of-cloud
Infrastructure org strategy, portfolio budget, board narratives → vp-of-infrastructure

Related skills

Need	Skill
VP cloud envelope and executive FinOps accountability	`vp-of-cloud`
TCO, NPV, migration and commit business cases	`cloud-economist`
Ledger, capex/OpEx, month-end close	`compute-accounting-manager`
Enterprise EA and org chargeback model	`enterprise-cloud-architect`
Tag enforcement and cost runbooks in ops	`cloud-engineer`
Hygiene execution (delete idle resources)	`cloud-system-administrator`
K8s cluster cost and rightsizing	`cluster-deployment-engineer`
LLM/token cost programs	`ai-token-improvement-plan-engineer`
AI ops cost and capacity	`ai-lead-ops`
Well-Architected cost pillar at design	`cloud-architect`
Business requirements for finance tools	`business-analyst`
VP infrastructure leadership	`vp-of-infrastructure`

Core Workflows

1. Scope and FinOps principles

Inform, optimize, operate; boundaries with accounting.

See references/finops_scope_and_principles.md.

2. Cost visibility and allocation

Tags, CUR, dashboards, allocation rules.

See references/cost_visibility_allocation.md.

3. Optimization and rightsizing

Waste, SKUs, commitments, engineering tickets.

See references/optimization_rightsizing.md.

4. Budgeting and forecasting

Budgets, forecasts, anomalies.

See references/budgeting_forecasting.md.

5. Unit economics and reporting

Cost per unit, executive narratives.

See references/unit_economics_reporting.md.

6. FinOps governance

Policies, RACI, review cadence.

See references/finops_governance.md.

Outputs

Cost breakdown — by account, service, tag, trend vs prior period
Optimization backlog — savings estimate, owner, risk, effort
Commitment recommendation — coverage %, term, break-even, risk
Allocation model — keys, untagged %, disputed splits
Forecast — baseline, growth drivers, confidence range
Anomaly report — root cause, one-time vs recurring

Principles

Everyone owns their spend — FinOps enables; engineering decides trade-offs
Unit economics over totals — tie cost to business drivers
Measure then commit — stabilize usage before multi-year RIs
Same tags as finance — align with compute-accounting-manager keys where possible
Fast feedback — weekly visibility beats quarterly surprises

Comments

Markdown supported

Details

Author: rade-nugroho
Repository: rade-nugroho/agentic-enteprises-skill
Category: Cloud & DevOps
Installs: 36
GitHub stars: 12

Report

More skills

All skills

lark-apps

open.feishu.cn

732.0k

Develop and host Miaoda (Spark/Miaoda) apps: app creation, local full-stack development, cloud generation and iteration, creative design (UI mockups / interactive prototypes / wireframes / landing pages / dashboards / slide decks / visual exploration), integration of AI-related capabilities, Feishu platform capabilities, or other external capabilities; log/Trace/monitoring metric/PV/UV queries; environment variable management; app collaborators and collaboration permissions; app roles and members; and automation triggers (scheduled / record changes / Webhook / Feishu approvals). Use when users want to develop or create a system, tool, platform, or app; develop locally or in the cloud, modify, deploy, publish, launch, or get a shareable link; create a page or website with HTML and deploy it to Miaoda; design, create a mockup, prototype, wireframe, PPT, deck, or visual exploration; or mention Miaoda/Spark/Miaoda apps (links like `/app/app_xxx` or `/page/<token>`, runtime domains like *.aiforce.cloud), app databases, app file storage, open API Keys, visibility, app collaborators/developer permissions, app roles/role members, production logs, API request volume, error volume, latency, traffic, environment variables, or setting up automation tasks, scheduled triggers, or approval-triggered automation for Miaoda apps. Not for regular cloud drive file uploads (lark-drive), Feishu document editing (lark-doc), or native slide creation (lark-slides).

azure-prepare

github.com/microsoft

571.7k

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.

wizard

github.com/mattpocock

571.5k

Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.

azure-ai

github.com/microsoft

571.2k

Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.