recipes
Use when a user states a FinOps *outcome* rather than a tool. Route to one recipe card, then hand off: bill jump → explain-period-change (DIGEST preview); clicked chart slice / explain this bar → explain-chart-slice; marketplace → marketplace-spend; K8s namespace → namespace-cost; credits runway → provider-credits; GCP spend CUD leftover → gcp-spend-cud; BigQuery warehouse → bigquery; YTD credits → credits-ytd-explore; weekly env+service pulse → service-cost-weekly; tag coverage → untagged-coverage; exec env report → env-costs-cto; explore Prod vs R&D → prod-vs-rnd-explore; build Prod/R&D VDIM → prod-vs-rnd-vdim; reallocate by external metric → reallocate-by-external-metric; budget vs actual daily → budget-vs-actual-dashboard; EC2 +10% alert → ec2-cost-spike-alert; compute drill-down → compute-drilldown-dimension. Skeletons in recipes; HOW in reports/dashboards/virtual-dimensions/query/bigquery.
Install
With your agent
Install OMGSkills skill "costory-io/costory-finops-mcp-skills:plugins/costory/skills/recipes" 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/recipes ~/.claude/skills/recipesFrom README
Recipes A recipe is a ready-made design for a common FinOps tracking goal — scope, split, period, widgets, delivery — as a payload skeleton, then a hand off to the mechanics skill (reports, dashboards, virtual-dimensions, query). Recipes never restate full delivery safety or live schema edge cases; fill placeholders after confirm, then build with the mechanics skill. How to use this skill Match the user's goal using Pick a recipe below (triggers + "not this if"). Read only that one file under plugins/costory/skills/recipes/. Run the card's Tool sequence through confirm gates — do not fire mutation/delivery tools until confirmed. Fill [PLACEHOLDERS] from discovery + user answers; keep frozen fields as written. Restate the Brief, then hand off the filled skeleton to the named mechanics skill. If nothing matches → fall through to reports (or the relevant mechanics skill) and design from scratch.
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,...
dashboards
Used when creating or extending Costory dashboards, generating interesting FinOps overviews (suggest_groupby +...