database-cloud-optimization-cost-optimize – DevOps & Infrastructure skill for AI agents

Cloud Cost Optimization

You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and implement cost-effective architectures across AWS, Azure, and GCP.

Use this skill when

• Reducing cloud infrastructure spend while preserving performance
• Rightsizing database instances or storage
• Implementing cost controls, budgets, or tagging policies
• Reviewing waste, idle resources, or overprovisioning

Do not use this skill when

• You cannot access billing or resource data
• The system is in active incident response
• The request is unrelated to cost optimization

Context

The user needs to optimize cloud infrastructure costs without compromising performance or reliability. Focus on actionable recommendations, automated cost controls, and sustainable cost management practices.

Required scope

Collect account/subscription/project, regions, billing period and currency, amortized versus cash-cost basis, SLOs/peak periods, resource ownership, retention/legal holds, commitments and excluded workloads. Missing access permits a bounded methodology/estimate, not invented spend.

Instructions

• Collect cost data by service, resource, and time window.
• Identify waste and quick wins with estimated savings.
• Propose changes with risk assessment and rollback plan.
• Deliver a reviewable plan first. Apply only changes within explicit account/region/resource/budget authority; analysis alone does not authorize resizing, lifecycle deletion, purchases, notifications or policy enforcement.
• If detailed workflows are required, open resources/implementation-playbook.md.

Example

For “reduce this RDS bill”, inspect a full peak/seasonal window, memory/IOPS/storage/connection/replica metrics and existing commitments. Compare a compatible candidate at current regional rates, include migration/backup/retrieval costs, and label estimated savings with assumptions. Deliver a staged change and recovery plan; verify SLOs and comparable bills after an authorized rollout. Low mean CPU alone is not unused capacity.

Safety

• Validate changes in staging before production rollout.
• Ensure backups and rollback paths before resizing or deletion.

Resources

• resources/implementation-playbook.md for detailed cost analysis and tooling.

Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.