agentleFS
rade-nugrohorade-nugroho/Agentic-Enteprises-Skill/cloud-economist/SKILL.md

cloud-economist

Skill9 starsChanged 6 months agoMITView on GitHub

Guides cloud economics—TCO and NPV for cloud vs on-prem or SaaS, pricing-model trade-offs (on-demand, commitments, spot), commitment portfolio economics, marginal cost and elasticity, regional and service cost comparisons, migration and architecture option business cases, and CFO-ready economic narratives tied to growth drivers. Use when building cloud business cases, comparing architectural cost options, sizing EA or commit programs economically, modeling 3–5 year spend scenarios, or explaining margin impact of cloud choices—not for monthly bill optimization (finops-analyst), GL close (compute-accounting-manager), hands-on tagging/rightsizing (finops-analyst), technical reference architecture (cloud-architect), or general non-cloud strategy consulting (business-consultant).

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run sensitivity analysis — usage growth, price changes, discount tiers, FX

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Cloud Economist

When to Use

  • Build TCO/NPV for cloud migration, repatriation, or hybrid
  • Compare economic options — serverless vs containers vs VMs, managed vs self-run, regions
  • Model commitment portfolio — coverage mix, term, break-even, flexibility value
  • Analyze marginal cost of scale (next 10k users, new region, new product line)
  • Quantify elasticity — cost at p50 vs p99 load; burst vs steady-state economics
  • Prepare EA or commit negotiation inputs (volume curves, alternative structures)
  • Run sensitivity analysis — usage growth, price changes, discount tiers, FX
  • Link cloud spend to gross margin and unit economics for product/finance
  • Evaluate multi-cloud cost of redundancy vs lock-in risk (economic framing)
  • Support cloud-architect and enterprise-cloud-architect ADRs with cost models

When NOT to Use

  • CUR analysis, idle resource cleanup, monthly budgets → finops-analyst
  • GL mapping, amortization, fixed assets → compute-accounting-manager
  • VPC design, landing zones, migration waves (technical) → cloud-architect
  • Org CCoE and EA program design → enterprise-cloud-architect
  • Cloud program portfolio, migration funding, executive EA sign-off → vp-of-cloud
  • Issue trees and operating model (non-cloud-specific) → business-consultant
  • Rack/GPU supply TCO in data centers → data-center-compute-supply-efficiency
  • Implement infra or purchase commits → cloud-engineer, finops-analyst
  • Deal-level sizing, RFP cost framing, build-vs-buy for a customer → solutions-architect

Related skills

NeedSkill
VP cloud spend envelope and EA commercial framevp-of-cloud
Operational FinOps and dashboardsfinops-analyst
Accounting and ledgercompute-accounting-manager
Cloud architecture and WAF cost pillarcloud-architect
Enterprise EA and org FinOpsenterprise-cloud-architect
Strategy consulting (general)business-consultant
Business model researchbusiness-model-researcher
Data platform TCOdata-architect
AI/token cost programsai-token-improvement-plan-engineer
Supply chain hardware TCOsupply-chain-manager
Customer deal cost framing and option comparisonsolutions-architect

Core Workflows

1. Scope and economic lens

Boundaries vs FinOps, architect, finance.

See references/cloud_economist_scope.md.

2. TCO and build vs buy

Cloud vs on-prem vs SaaS; NPV framework.

See references/tco_build_vs_buy.md.

3. Commitment portfolio economics

RI/SP/CUD/EA economic trade-offs.

See references/commitment_portfolio_economics.md.

4. Marginal cost and elasticity

Scale economics and demand shapes.

See references/marginal_cost_and_elasticity.md.

5. Scenario and sensitivity modeling

What-if and risk ranges.

See references/scenario_sensitivity_modeling.md.

6. Executive economic briefings

CFO and board narratives.

See references/executive_economic_briefings.md.

Outputs

  • Economic model — assumptions, 3–5 year cash flows, NPV/IRR where applicable
  • Option comparison table — cost, flexibility, risk, break-even
  • Commitment recommendation memo — coverage, term, $ at risk, exit cost
  • Sensitivity chart — drivers ranked by impact on spend or margin
  • One-pager for ADR — recommended option with economic rationale
  • Negotiation brief — volume forecast, walk-away, alternative structures

Principles

  • Explicit assumptions — growth, utilization, discount, labor, egress
  • Compare options at equal SLO — do not trade reliability without pricing risk
  • Time value matters — NPV for multi-year commits and migrations
  • Flexibility has value — price the option to scale down or pivot
  • Hand off execution — economist models; finops-analyst operationalizes

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.