cost-optimization

Optimize cloud spending across AWS, Azure, GCP, and OCI using rightsizing, tagging, and reserved capacity.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/SanketAdlak/PDMProjectDesign --skill cost-optimization-sanketadlak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cost-optimization
Source: https://github.com/SanketAdlak/PDMProjectDesign/tree/main/.agents/skills/cost-optimization
Command: npx skills add https://github.com/SanketAdlak/PDMProjectDesign --skill cost-optimization-sanketadlak

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Cloud bills grow quickly when resources are over-provisioned, untagged, or left running idle. This Skill provides a structured framework for reducing cloud expenses across AWS, Azure, GCP, and OCI without sacrificing performance or reliability. ## Core Features & Use Cases - Multi-Cloud Cost Strategies: Concrete guidance on Reserved Instances, Savings Plans, Spot/Preemptible instances, Committed Use Discounts, and OCI flexible shapes. - Tagging and Governance: Standardized tagging conventions with Terraform examples and a dedicated tagging standards reference for cost allocation and chargeback. - Monitoring and Alerts: Ready-to-use Terraform snippets for AWS Budgets, cost anomaly detection, and auto-scaling policies. - Use Case: A platform team facing a 40% month-over-month AWS bill increase can apply the right-sizing checklist, implement S3 lifecycle policies, and purchase Savings Plans to bring spending back under budget. ## Quick Start Ask the AI to analyze your current cloud infrastructure and produce a cost optimization plan with rightsizing recommendations and budget alerts.

Frequently Asked Questions about cost-optimization

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

FAQPage Schema
How do I reduce AWS cloud costs?

Reduce AWS costs by right-sizing instances based on utilization, purchasing Reserved Instances or Savings Plans for steady workloads, using Spot Instances for batch jobs, and applying S3 lifecycle policies to move data to cheaper storage tiers. Enable Cost Anomaly Detection and budget alerts to catch overspending early.

What is the difference between Reserved Instances and Savings Plans?

Reserved Instances commit you to specific instance configurations for 1 or 3 years with up to 72% savings. Savings Plans offer similar discounts but apply flexibly across instance families, regions, and services like EC2, Fargate, and Lambda based on hourly spend commitment.

Does this cost optimization approach work for Azure and GCP?

Yes, the framework covers Azure Reserved VM Instances, Azure Hybrid Benefit, GCP Committed Use Discounts, Sustained Use Discounts, and Preemptible VMs, plus OCI flexible shapes and budgets. Each provider section includes provider-specific savings mechanisms and native cost tools.

How do I implement cost allocation tagging in Terraform?

Define a common_tags local with Environment, Project, CostCenter, Owner, and ManagedBy keys, then merge it into each resource's tags. The references/tagging-standards.md file documents required tags and enforcement practices like policy validation and weekly audits.

When should I use Spot or Preemptible instances?

Use Spot or Preemptible instances for interruption-tolerant workloads like batch processing, CI/CD, and stateless services, where savings reach 80-90%. Mix them with On-Demand capacity for critical services since Spot instances can be reclaimed with short notice.