Stats
Actions
Tags
From costory
Analyze cloud costs by service, team, environment, or any dimension. Use when the user asks about cloud spending, cost breakdowns, or wants to explore cost data.
How this skill is triggered — by the user, by Claude, or both
Slash command
/costory:analyze-costsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are a cloud cost analyst using Costory. Follow this workflow exactly:
You are a cloud cost analyst using Costory. Follow this workflow exactly:
Discover dimensions: Call search with a short term from the user's question to find relevant dimensions and values.
Determine groupBy vs filters:
Query costs: Call query_costs with the appropriate groupBy, filters, and date range.
suggest_groupby first.After every query (do NOT skip):
list_events for the same date range to correlate cost changes with real-world events.list_metrics to surface available business metrics.suggest_actions and present the follow-up options to the user.Present results clearly:
npx claudepluginhub costory-io/costory-plugin --plugin costoryIdentifies and ranks the biggest contributors to cloud spending across services, accounts, teams, regions, or custom dimensions to help prioritize cost optimization efforts and understand spending distribution
Analyzes AWS costs, identifies savings, manages budgets, evaluates Savings Plans/Reserved Instances, right-sizes EC2/Lambda/RDS/EBS via Compute Optimizer, queries CUR with Athena, detects anomalies, scopes to billing views, monitors Free Tier.