---
name: cloud-spend-advisor
description: "A prioritised cloud cost-cutting plan for AWS, Azure or Google Cloud that holds performance, reliability and security steady, with savings estimates. Use when an engineering or finance lead wants a ranked list of ways to cut cloud spend while keeping performance and reliability intact. Do not use for a cloud migration plan or a security audit of the infrastructure. Related topics: cloud, devops, finance."
---

# Cloud Spend Advisor

A prioritised cloud cost-cutting plan for AWS, Azure or Google Cloud that holds performance, reliability and security steady, with savings estimates.

## When to use

Use this skill when an engineering or finance lead wants a ranked list of ways to cut cloud spend while keeping performance and reliability intact. Do not use it for a cloud migration plan or a security audit of the infrastructure.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Map the spend, workloads and services to the likeliest sources of waste for the stated concerns.
3. Screen out any change that would breach the performance, reliability or compliance needs.
4. Rank the remaining recommendations by saving against effort and risk, within the chosen time horizon.
5. For each, state the change, the expected saving if requested, the performance risk if requested and a way to verify it.
6. Present the list in the chosen layout and detail level, labelling estimates as estimates.

## Inputs

- **Providers** (choose any: AWS, Azure, Google Cloud, Other)
- **If other, which** (free text, e.g. "Oracle Cloud or Alibaba Cloud")
- **Monthly spend** (free text, e.g. "For example 15000 USD")
- **Workloads** (choose any: Web applications, APIs, Data processing, Machine learning, Databases, Batch jobs, Internal tools, IoT, Other)
- **Services in use** (longer free text)
- **Performance needs** (longer free text)
- **Reliability targets** (longer free text)
- **Security and compliance** (longer free text)
- **Main cost concerns** (choose any: Compute, Storage, Networking, Databases, Data transfer, Licensing, Managed services, Idle resources, Unused resources)
- **Known pain points** (longer free text)
- **Priority areas** (longer free text)
- **Time horizon** (choose one: Quick wins within a month, Within three months, Within a year, Beyond a year, All horizons)
- **Detail level** (choose one: High-level overview, Actionable steps with impact, Detailed technical guidance)
- **Layout** (choose one: Bulleted list, Numbered steps, Table, Executive summary with breakdown)
- **Estimate savings** (choose one: Yes, No)
- **Estimate performance impact** (choose one: Yes, No)
- **Focus on** (choose any: Rightsizing, Commitment discounts, Spot instances, Serverless, Storage tiering, Network optimisation, Database optimisation, Automation, Cost governance)

## Output

A ranked list of recommendations in the chosen layout, each with change, estimated saving, risk and verification, plus a note on assumptions.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Cloud Spend Advisor

Analyse my cloud setup and recommend cost reductions without hurting performance, reliability or security.

Environment
- Providers: {{Providers}}
- If other, which: {{If other, which}}
- Monthly spend: {{Monthly spend}}
- Workloads: {{Workloads}}
- Services in use: {{Services in use}}

Requirements
- Performance needs: {{Performance needs}}
- Reliability targets: {{Reliability targets}}
- Security and compliance: {{Security and compliance}}

Concerns
- Main cost concerns: {{Main cost concerns}}
- Known pain points: {{Known pain points}}
- Priority areas: {{Priority areas}}

Preferences
- Time horizon: {{Time horizon}}
- Detail level: {{Detail level}}
- Layout: {{Layout}}
- Estimate savings: {{Estimate savings}}
- Estimate performance impact: {{Estimate performance impact}}
- Focus on: {{Focus on}}

Rank recommendations by savings against effort and risk. For each give the change, the services it touches, the expected saving, the risk to performance or reliability, and how to verify nothing regressed. Mark any trade-off explicitly and skip anything that would breach the stated reliability or compliance needs. Say which figures are estimates from the spend given.

## Pitfalls

- Recommending reserved capacity for a workload that may shrink, which locks in cost.
- Rightsizing on average usage while ignoring peaks, which causes slowdowns.
- Quoting precise savings from a single monthly spend figure with no usage data.
