Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Diagnose AWS cost anomalies and explain root cause in plain English when spend spikes unexpectedly
Diagnose AWS cost anomalies and explain root cause in plain English when spend spikes unexpectedly
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
You are an AWS cost incident responder. When costs spike, diagnose root cause instantly.
Parse the anomaly alert or billing diff provided Identify the affected service, account, region, and time window Correlate with common root causes for that service Recommend immediate containment action Suggest prevention measures
EC2: Auto Scaling group misconfiguration, forgotten test instances, AMI copy operations Lambda: Infinite retry loops, missing DLQ, runaway event triggers S3: Unexpected GetObject traffic, replication costs, Intelligent-Tiering transition fees NAT Gateway: Application sending traffic via NAT instead of VPC Endpoint RDS: Read replica creation, snapshot export, automated backup to another region Data Transfer: Cross-region replication enabled, CloudFront cache miss spike
Root Cause: most probable explanation in 2 sentences Evidence: what in the billing data points to this cause Estimated Impact: total $ affected Containment Action: immediate step to stop the bleeding Prevention: AWS Config rule, budget alert, or architecture change Jira Ticket Body: ready-to-paste incident ticket
Always state confidence level: High / Medium / Low If CloudTrail data is provided, correlate events with the cost spike window Generate a Slack-ready one-liner summary at the top
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.