finops-review

Annotate cloud cost implications of architectural decisions with Terraform-style annotations.

23|7|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/kinncj/MAPLE --skill finops-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finops-review
Source: https://github.com/kinncj/MAPLE/tree/main/template/.opencode/skills/finops-review
Command: npx skills add https://github.com/kinncj/MAPLE --skill finops-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and annotate the cloud cost implications of architectural decisions, helping teams make economical design choices during reviews.

Core Features & Use Cases

  • Identify cost drivers across Compute, Storage, Networking, and Third-party APIs to forecast and compare architectural options.
  • Use Terraform-style annotations to embed cost considerations directly into infrastructure code.
  • Leverage architecture review questions and a monthly estimate template to plan and validate cost outcomes.

Quick Start

Run the finops-review skill during a design review to annotate cost implications.

Frequently Asked Questions about finops-review

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

FAQPage Schema
How do I estimate cloud costs for architectural decisions during a design review?

To estimate cloud costs for architectural decisions, you can annotate infrastructure designs by categorizing cost drivers across compute, storage, networking, and third-party APIs. This provides a structured monthly cost estimate template to compare architectural options.

What are the primary cloud cost drivers I should analyze for infrastructure cost optimization?

The primary cloud cost drivers to analyze for infrastructure cost optimization are compute, storage, networking, and third-party APIs. Identifying these categories during architectural reviews helps teams forecast and validate cost outcomes.

Can I embed cost estimates directly into Terraform infrastructure code?

Yes, you can embed cost estimates into Terraform infrastructure code using Terraform-style annotations. This approach embeds cost considerations directly into infrastructure code during design sessions and cost-optimization planning.

How do I forecast monthly cloud expenses for new services?

You forecast monthly cloud expenses for new services by applying architecture review questions and a monthly estimate template. This validates cost outcomes and categorizes specific cost drivers like compute, storage, and third-party APIs.

Does this approach work for reviewing existing infrastructure or only for new design sessions?

This approach works for both existing infrastructure reviews and new service design sessions. It applies cost-optimization planning across compute, storage, networking, and third-party APIs to annotate cost implications.