cur-data

Explain AWS Cost and Usage Report file formats and column structures.

1|Updated Nov 5, 2025
One-click install
npx skills add https://github.com/T-Klug/aws-cur-report-generator --skill cur-data
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cur-data
Source: https://github.com/T-Klug/aws-cur-report-generator/tree/main/.claude/skills/cur-data
Command: npx skills add https://github.com/T-Klug/aws-cur-report-generator --skill cur-data

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides essential knowledge about the structure, column formats, and common analysis patterns for AWS Cost and Usage Reports (CUR), enabling users to effectively interpret and utilize their AWS billing data.

Core Features & Use Cases

  • File Format Understanding: Explains support for CSV, CSV.GZ, and Parquet formats.
  • Column Name Normalization: Details how canonical column names map to older and newer CUR formats.
  • Key Cost Metrics: Identifies crucial columns like unblended_cost, blended_cost, and net_unblended_cost.
  • Line Item Type Definitions: Clarifies the meaning of various line_item_type values.
  • Discount & Savings Plan Insights: Guides on identifying discounts and analyzing Savings Plan effectiveness.
  • Common Aggregations: Provides examples for grouping costs by service, account, date, and month.
  • Anomaly Detection: Explains the z-score method used for identifying unusual spending.
  • Mock Data Reference: Describes the structure and content of the mock data used for testing.

Quick Start

Explain the different AWS CUR file formats supported by the tool.

Frequently Asked Questions about cur-data

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the data structure of the AWS Cost and Usage Report (CUR)?

The AWS Cost and Usage Report (CUR) data structure contains billing data in CSV, CSV.GZ, or Parquet formats, featuring canonical column names that map to older and newer variants for tracking costs and usage metrics.

How do I identify discounts and Savings Plans in AWS CUR billing data?

To identify discounts and Savings Plans in AWS CUR billing data, you analyze specific line item types and key cost metrics like net_unblended_cost to evaluate Savings Plan effectiveness and applied discount patterns.

What is the best way to aggregate AWS cost data by service and account?

Aggregating AWS cost data by service, account, date, and month requires grouping specific CUR columns, utilizing canonical cost metrics like unblended_cost or blended_cost to summarize total billing expenditures accurately.

Does AWS CUR support Parquet format for cost analysis reporting?

AWS CUR supports Parquet, CSV, and CSV.GZ file formats for cost analysis reporting, enabling efficient querying and columnar data processing for large-scale billing datasets.

How do I detect spending anomalies in AWS CUR data using z-scores?

Detecting spending anomalies in AWS CUR data using z-scores involves calculating standard deviations from your historical cost metrics to identify unusual variations and outliers in your AWS billing patterns.

Why do CUR column names differ between older and newer AWS billing reports?

CUR column names differ between older and newer AWS billing reports due to format updates, requiring column name normalization to map canonical names correctly when analyzing historical cost data structures.