dashboards
Use when creating or extending Costory dashboards, generating interesting FinOps overviews (suggest_groupby + suggest_usage_metrics + text widgets), adding or replacing widgets, copying widgets between dashboards, editing dashboardContext (global filter / period / groupBy) via update_dashboard, or applying shared-context inheritance for period, groupBy, metric, currency, and CEL filters. Call get_skill with skillId "dashboards" before create_dashboard or update_dashboard.
Install
With your agent
Install OMGSkills skill "costory-io/costory-finops-mcp-skills:plugins/costory/skills/dashboards" 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/dashboards ~/.claude/skills/dashboardsFrom README
Dashboards A DashboardV2 has a shared dashboardContext input (global theme) and widgets that inherit it by default. Each widget is either a chart (Advanced Explorer queries + chartType) or a text block (type: "text", textContent). Context-first rule: define the full dashboardContext before listing widgets. Widgets should contain only overrides — never duplicate what already lives in dashboardContext. If two or more widgets share the same period, groupBy, metric, currency, or filter scope, extract that shared value to dashboardContext first. Temporary compatibility: the deprecated top-level context alias is accepted during migration, but always generate dashboardContext. Never send both.
More from this repo
bigquery
Used when the user asks about BigQuery costs, SKUs, on-demand Analysis vs capacity slots/editions, leftover on-demand,...
cost-change-investigation
Used when investigating a cost change to explain what changed, when, and the best-supported drivers with contribution,...
recipes
Used when a user states a FinOps *outcome* rather than a tool.