ericyanpek/agentcore-private-registry-blueprint / skill-package/src/aws_cost_anomaly_triage/skill_files
aws-cost-anomaly-triage
VerifiedUse when the user reports an unexpected AWS cost spike, an alert from AWS Cost Anomaly Detection, or asks "why did my AWS bill go up". Walks through a structured triage SOP using Cost Explorer, CUR, and service-specific signals before recommending remediation.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.4 KB |
| resources/anomaly-patterns.md | markdown | 1.9 KB |
| resources/confounders.md | markdown | 1.6 KB |
| resources/per-service-drilldown.md | markdown | 1.4 KB |
| resources/postmortem-template.md | markdown | 864 B |
| resources/remediation-playbook.md | markdown | 2.1 KB |
| resources/thresholds.md | markdown | 623 B |
resources/anomaly-patterns.md
View on GitHub# Anomaly pattern library
Ordered by historical frequency in our environment. Match the
observed signals to the closest pattern, then jump to its drilldown
section in `per-service-drilldown.md`.
## Pattern A — Compute scale-up
- Signals: EC2/Fargate/Lambda usage hours up, new instance IDs in
CloudTrail, autoscaling activity in CloudWatch
- Common causes: load test left running, autoscaling min capacity
raised, new service deployed without rightsizing
- First check: CloudTrail `RunInstances` / `CreateService` /
`CreateFunction` events
## Pattern B — Data transfer surge
- Signals: `DataTransfer-Out-Bytes` or `NatGateway-Bytes` line items up
- Common causes: cross-AZ chatter from a new microservice, S3 download
from outside region, missing VPC endpoint
- First check: VPC Flow Logs aggregated by `dstaddr` for the affected
AZ/region
## Pattern C — Storage creep
- Signals: S3 `TimedStorage-ByteHrs` or EBS `VolumeUsage` up
- Common causes: lifecycle policy missing, snapshot retention ramping,
backup-AMI accumulation
- First check: S3 Storage Lens dashboard, `aws ec2 describe-snapshots`
## Pattern D — New service activation
- Signals: brand-new service line item appears
- Common causes: someone enabled Bedrock / OpenSearch / Aurora /
GuardDuty without approval; trial period ended
- First check: CloudTrail across all regions for the service's
`Create*` events
## Pattern E — Tagging gap closure
- Signals: tagged-cost goes up by amount equal to drop in
untagged-cost
- Common causes: tagging policy enforcement, automation backfill
- First check: Cost Explorer grouped by tag `team` (or your equivalent)
with "Show untagged" enabled
## Pattern F — Discount expiration
- Signals: net cost up but usage unchanged
- Common causes: SP/RI expiring, EDP/PPA renegotiation, credit
exhausted
- First check: Billing Console → Cost Management → Reservations &
Savings Plans → expirations
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |