What problem does it solve? Investigating AWS spend anomalies and proposing cost optimizations is risky because billing data is delayed, estimated, and sensitive, and premature changes to resources, budgets, or commitments can cause outages or financial lock-in. This Skill enforces a read-only, evidence-first workflow before any cost-related change. ## Core Features & Use Cases - Read-only cost baseline: Verifies account identity and billing scope, then queries Cost Explorer or CUR with documented metrics, time windows, and groupings. - Evidence-backed recommendations: Separates observations from interventions, requiring utilization, SLO, and allocation evidence before suggesting rightsizing, tagging fixes, or commitment purchases. - Approval gates for changes: Requires explicit confirmation and a structured risk/verification/rollback plan before modifying budgets, IAM, exports, resources, or Savings Plans/Reserved Instances. - Use Case: When a monthly AWS bill spikes unexpectedly, use this Skill to identify the accountable account scope, reproduce the anomaly with a bounded Cost Explorer query, and present a verified recommendation with rollback criteria instead of deleting resources on cost data alone. ## Quick Start Use the aws-finops skill to investigate why our AWS spend increased last month and propose safe optimization options.
