Skip to content
Skills Library
DevOps & cloud · Analysis

cloud-cost-optimization

/cloud-cost-optimization

Cut cloud spend with tagging, rightsizing, commitment mix, and egress awareness, without breaking reliability. Use when the cloud bill needs reducing or a cost-review practice needs standing up.

Repository
AI-SKILLS ↗
Licence
MIT
Last repository change
05.09.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 05.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Cut cloud spend with tagging, rightsizing, commitment mix, and egress awareness, without breaking reliability. Use when the cloud bill needs reducing or a cost-review practice needs standing up.

Original author description

Cut cloud spend with tagging, rightsizing, commitment mix, and egress awareness, without breaking reliability. Use when the cloud bill needs reducing or a cost-review practice needs standing up.

How it works

  1. Method
  2. Boundaries
Original SKILL.md headings · 51 lines, 376 words
SKILL.md preview
---
name: cloud-cost-optimization
description: Cut cloud spend with tagging, rightsizing, commitment mix, and egress awareness, without breaking reliability. Use when the cloud bill needs reducing or a cost-review practice needs standing up.
---

# Cloud cost optimization

You cannot cut what you cannot attribute. Visibility first, then the
big three levers: rightsizing, commitments, and storage lifecycle;
everything else is decoration until those are done.

## Method

1. **Attribute before optimizing.** Enforce tags (team, service, env)
   at provision time via IaC policy, not wiki pleading; untagged
   resources get a weekly report and an owner hunt. Turn on the billing
   export to a queryable store; the console's month view hides the
   per-service trends you need.
2. **Rightsize from utilization, not fear.** Pull 30 days of p95
   CPU/memory per instance; anything under ~40% at p95 drops a size
   (halving cost per step). Do the same for provisioned IOPS,
   over-replicated dev databases, and idle load balancers. Schedule
   non-prod to sleep nights and weekends: 70% of the week is off-hours.
3. **Buy commitments for the floor, spot for the burst.** Cover the
   stable baseline (12 months of history says what that is) with
   savings plans/reserved capacity at 60-70% coverage; leave headroom
   on-demand. Fault-tolerant batch and CI go on spot at 60-90% off,
   with interruption handling tested (see kubernetes-workloads for
   disruption budgets).
4. **Lifecycle the storage.** Objects: transition to infrequent-access
   after 30 days, archive after 90, delete what compliance does not
   require (see data-retention); abort incomplete multipart uploads.
   Snapshots and orphaned volumes/IPs are the classic silent leak:
   sweep monthly.
5. **Respect egress and cross-zone gravity.** Data leaving the provider
   or crossing regions costs more than compute reading it in place.
   Process where data lives, cache at the edge, and check NAT gateway
   processing charges: a chatty service behind NAT can out-cost its
   instances.
6. **Institutionalize the loop.** Unit economics metric (cost per
   request/customer/GB) on a dashboard, anomaly alerts on daily spend,
   a monthly 30-minute review per team with the top-5 movers, and cost
   as a line item in design reviews (see architecture-review-board).
   One-off cleanups decay in a quarter; the loop does not.

## Boundaries

- Do not trade reliability invisibly: dropping multi-AZ, backups, or
  headroom is a risk decision for the service owner, not a cost
  optimizer's line edit.
- Engineering time is a cost too; a week of work to save $40/month
  fails its own review.
- Provider pricing shifts and this skill's ratios drift; re-verify
  numbers against current price sheets before big commitments.

Versions

RepositoryScoreLicence
This page · Amey-Thakur/AI-SKILLS90MIT
reddygopalkrishna/developer-agent-skills100MIT

Database snapshot: 13.11.2026 · package version 29122c815e4a (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100cost-optimization
    Audit and reduce infrastructure and tooling costs without sacrificing reliability or velocity. Use this skill when reviewing monthly cloud or SaaS spend, finding unused resources, rightsizing infrastructure, negotiating vendor contracts, deciding what to consolidate, or planning…
  • 100aws-cost-optimization
    Reduce AWS spend with rightsizing, autoscaling, commitment planning, and storage lifecycle policies. Use when running FinOps reviews, lowering cloud bills, or improving cost-per-request metrics.
  • 100aws-cost-optimization
    Reduce AWS spend with rightsizing, autoscaling, commitment planning, and storage lifecycle policies. Use when running FinOps reviews, lowering cloud bills, or improving cost-per-request metrics.
  • 100aws-cost-optimization
    Reduce AWS spend with rightsizing, autoscaling, commitment planning, and storage lifecycle policies. Use when running FinOps reviews, lowering cloud bills, or improving cost-per-request metrics.
  • 100cost-optimization
    Cuts cloud spend without cutting reliability by finding the few levers that move most of the bill — idle and orphaned resources, over-committed on-demand spend that qualifies for reserved or savings-plan discounts, and oversized fleets — and going after them in dollar order. Use…
  • 90aws-waf-cost-optimization-review
    Review AWS workload cost posture against the Well-Architected Framework Cost Optimization Pillar. Covers cost visibility, tagging compliance, commitment coverage, rightsizing, Spot and managed service adoption, and idle resource identification. Use when auditing cloud spend,…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.