Skip to content

ericyanpek/agentcore-private-registry-blueprint / skill-package/src/aws_cost_anomaly_triage/skill_files

aws-cost-anomaly-triage

Verified

Use 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.

resources/confounders.md

View on GitHub
# Confounders to rule out before classifying an anomaly

These factors regularly cause **apparent** cost spikes that are not
actually anomalous. Confirm each is not the explanation before
proceeding to Step 2 (Classify).

## RI / SP amortization timing
Reserved Instance / Savings Plan upfront fees are amortized monthly,
but credit application timing can shift line items between days.
Compare amortized cost (Cost Explorer → "Amortized cost" view) with
unblended cost — if they diverge, the anomaly is in the unblended view
only and should be ignored.

## Credit consumption / expiration
A credit running out causes a step-function increase in net cost
without any underlying usage change. Check Billing Console → Credits
for any credit that expired in the anomaly window.

## Refund / reversal posting
AWS occasionally posts refunds or correction line items days after the
fact. A negative line item from last month being reversed appears as a
positive anomaly today. Filter Cost Explorer to "Refunds" charge type
to inspect.

## Linked account onboarding
A newly added member account in AWS Organizations can introduce
significant cost that looks like an anomaly at the management account
level but is expected at the organization level.

## Tag remediation surfacing
When a tagging gap is closed (e.g., previously untagged S3 buckets get
tagged), cost shifts from "untagged" to a specific team. Net cost is
unchanged at the org level but appears as a per-team anomaly.

## Currency / billing region change
Cross-region transfers between AWS billing entities (e.g., AISPL in
India) can create one-time line items. Rare but happens.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 119kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall