cost-analysis

Attribute cloud costs to projects and services from billing exports.

3|Updated May 28, 2026
One-click install
npx skills add https://github.com/mahg-es/araya --skill cost-analysis-mahg-es
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cost-analysis
Source: https://github.com/mahg-es/araya/tree/main/skills/cost-analysis
Command: npx skills add https://github.com/mahg-es/araya --skill cost-analysis-mahg-es

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cloud cost information remains opaque without structured analysis; this skill breaks out spend by service, project, and environment to reveal drivers and optimization opportunities.

Core Features & Use Cases

  • Attribute costs to projects via tags and environments; identify top spend areas; propose savings.
  • Compare month-over-month and detect anomalies; generate actionable reports for budgeting.
  • Use case: monthly cloud billing review to drive cost optimization across AWS, OCI, and Hetzner.

Quick Start

Analyze your cloud bill by project and service to identify top cost drivers and optimization opportunities.

Frequently Asked Questions about cost-analysis

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

FAQPage Schema
How do I analyze multi-cloud billing exports to identify top cost drivers?

Multi-cloud billing analysis requires inputting billing exports, tags, and environment mappings to attribute cloud costs to specific projects and services, revealing top cost drivers and optimization opportunities.

Can I use this cost-analysis skill to detect month-over-month cloud billing anomalies?

Yes, cost-analysis compares month-over-month cloud billing data to detect anomalies, generating structured reports by service and project to support budget planning and actionable cost optimization.

Does this approach work for cost optimization across AWS, OCI, and Hetzner environments?

Yes, this cost optimization approach applies to multi-cloud environments, supporting monthly cloud billing reviews and cost attribution across platforms including AWS, OCI, and Hetzner.

What data do I need to attribute cloud costs to projects and environments?

To attribute cloud costs to projects and environments, you need to provide input data such as cloud billing exports, resource tags, and environment mappings for accurate cost breakdown.

What is the best way to break down opaque cloud costs for budget planning?

The best way to break down opaque cloud costs is structurally attributing spend by service, project, and environment to reveal underlying drivers and propose actionable savings opportunities.

Are there limitations when analyzing cloud costs without structured tagging?

Without structured tagging and environment mappings, cloud cost information remains opaque, limiting the ability to accurately attribute spend to projects and reveal specific cost drivers.