SkillVaultskills Browse all 1,000+ skills

FinOps · Version 1.5.0 · Reviewed 2026-08-02

Reserved Capacity Portfolio Advisor

Reduce waste without harming reliability in commitment sizing and utilization-risk analysis with evidence, explicit trade-offs, and a verification plan.

4 method steps 5 documented failure modes 4 diagnostic checks 7 quality gates

Builds commitment portfolios from stable workload baselines, growth uncertainty, regional flexibility, utilization risk, and on-demand safety margins.

₹199 one-time

Get this skill archive

Install in your AI coding tool

SkillVault packages this skill in the open Agent Skills format for five leading coding tools, with a raw SKILL.md fallback for every other compatible IDE or agent.

See the complete graphical installation and usage guide

What this skill helps you do

  • Commitment sizing
  • Utilization-risk analysis
  • Coverage planning

How Reserved Capacity Portfolio Advisor works

You provide

Cost breakdown by tag, utilization data, and growth trend

It inspects

Unit cost and idle capacity behind commitment sizing

It decides

A utilization-risk analysis action with a reliability guardrail

You verify

Cost per unit of business work tracked after the change

What it checks first

Reserved Capacity Portfolio Advisor builds commitment portfolios from stable workload baselines, growth uncertainty, regional flexibility, utilization risk, and on-demand safety margins. Use it when the work involves Commitment sizing, Utilization-risk analysis, Coverage planning.

  1. Unit cost per business transaction rather than total spend, since total rises with healthy growth.
  2. The split between compute, storage, network egress, and managed-service premiums.
  3. Idle versus utilized capacity, which separates a sizing problem from an architecture problem.
  4. Whether cost scales with traffic, with data retained, or simply with elapsed time.

Failure modes it recognizes

  • Storage growing indefinitely because nothing was ever given a lifecycle or expiry policy.
  • Cross-zone traffic billed in both directions between services that could have been zone-aligned.
  • Orphaned resources such as unattached volumes, idle load balancers, and old snapshots with no owner.
  • Log and metric retention growing until observability costs exceed the workload it observes.
  • Reserved capacity committed before the workload shape was stable.

Answers it will reject

  • Cutting redundancy to save money, which trades a predictable bill for an unpredictable outage.
  • Optimizing the largest line item when a smaller one has worse unit economics and faster growth.
  • Reporting savings without a reliability guardrail, so a regression is discovered by customers.

Decision rules it applies

  • Attribute cost to a team or product before optimizing; unattributed cost never gets reduced.
  • Prefer eliminating waste over renegotiating price, because waste compounds and discounts do not.
  • Every cost reduction states its reliability guardrail and how a regression would be detected.

Evidence it asks for

  • Break cost down by tag and service, and report cost per thousand units of business work.
  • Compare requested against used resources over a full business cycle.
  • Track the trend of unit cost, since flat unit cost during growth is the success condition.

The method inside

  1. Map the artifact, actors, boundaries, and invariants relevant to commitment sizing.
  2. Trace concrete failure or abuse paths for utilization-risk analysis; do not report checklist items without a mechanism.
  3. Prioritize coverage planning findings by impact, likelihood, confidence, and cost of correction.
  4. Recommend the smallest defensible change, then define how an independent reviewer can verify it.

Deliverables

  • Commitment sizing assessment
  • Utilization-risk analysis decision and action plan
  • Coverage planning verification checklist

Evidence requirements

  • Itemized cost and usage data
  • Traffic, utilization, growth, and commitments
  • SLOs, architecture, and unit economics

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Recommend a one-year compute commitment strategy for workloads growing between ten and forty percent with seasonal peaks.

Expected output

Commit only against the conservative always-on baseline, preserve on-demand capacity for growth and peaks, and diversify purchase timing so renewal risk is not concentrated. Model coverage and utilization separately before optimizing headline discount...

Boundaries and compatibility

Ideal for

  • Commitment sizing: produce a decision or artifact grounded in supplied evidence.
  • Utilization-risk analysis: produce a decision or artifact grounded in supplied evidence.
  • Coverage planning: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Cutting redundancy without an SLO decision
  • Presenting list prices as realized savings

Agent compatibility

  • GitHub Copilot Agent Skills
  • Cursor Agent Skills
  • Claude Code Skills
  • OpenAI Codex Skills
  • JetBrains Junie Skills

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.