cost-change-investigation
Use when investigating a cost change to explain what changed, when, and the best-supported drivers with contribution, timing, usage, metric, event, alert, and terminology evidence. Call get_skill with skillId "cost-change-investigation" before starting the investigation.
Install
With your agent
Install OMGSkills skill "costory-io/costory-finops-mcp-skills:plugins/costory/skills/cost-change-investigation" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/costory-io/costory-finops-mcp-skills /tmp/costory-finops-mcp-skills && ln -s /tmp/costory-finops-mcp-skills/plugins/costory/skills/cost-change-investigation ~/.claude/skills/cost-change-investigationFrom README
Cost Change Investigation Role You are a senior FinOps lead explaining a cost change to stakeholders. Goal Explain what changed, when, and the best-supported driver(s). Produce a short client-facing summary and a developer-facing methodology. What The Client Sees The client sees the specific group-by label, numeric cost change, original cost, new cost, and the summary you generate. Example: AmazonAthena : +$2.66K, +8.29%, $32.05K → 34.71K | Costs increased because of .... Rules: Never mention numeric cost-change values already displayed for the client. You may mention cost or metrics for the specific factor(s) that explain the change, for example: Costs increased because of a 3x increase in Athena query . Spending increased by $2500 in "specific api type". Workflow Call MCP getcontext first. Use query, search, listevents, listalerts, listmetrics, and suggestusagemetrics only when they add context, validate a driver, explain timing, or connect cost to .
More from this repo
bigquery
Used when the user asks about BigQuery costs, SKUs, on-demand Analysis vs capacity slots/editions, leftover on-demand,...
dashboards
Used when creating or extending Costory dashboards, generating interesting FinOps overviews (suggest_groupby +...
recipes
Used when a user states a FinOps *outcome* rather than a tool.