bigquery
Use when the user asks about BigQuery costs, SKUs, on-demand Analysis vs capacity slots/editions, leftover on-demand, physical vs logical storage, time travel or fail-safe, streaming ingest, load/import jobs consuming a reservation, dbt or job labels, slot cost reallocation, dataset/table storage allocation, or unlabeled expensive queries. Call get_skill with skillId "bigquery" before investigating BigQuery spend or cloning the [BigQuery] dashboard. Not for GCP spend-based CUDs (recipes gcp-spend-cud).
Install
With your agent
Install OMGSkills skill "costory-io/costory-finops-mcp-skills:plugins/costory/skills/bigquery" 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/bigquery ~/.claude/skills/bigqueryFrom README
BigQuery Invoice SKUs first. Bytes scanned, slot-ms, and table storage are not on the bill. Teach slots vs on-demand, open [BigQuery] BigQuery Dashboard, then allocate or optimize. Not this if: GCP spend CUD leftover → recipes → gcp-spend-cud. Generic Explorer → query. Whole-bill "what changed" → recipes → explain-period-change. Workflow getcontext — currency; note bq / useremail if already ingested Several organizations: if getcontext returns "Multiple organizations" with a list of slugs, do not pick one. Ask the user which org to use (from that list or listorganizations), then pass that slug to getcontext and the following tool calls. If the user already named the org (e.g. "org acme"), use that slug directly. search { type: ["dashboards"], query: "BigQuery" } — use the template [BigQuery] BigQuery Dashboard. Org copies can differ. Never hardcode an id. get that template for the URL. Do not walk widgets. Teach Slots vs on-demand (two sentences): On-demand = pay per TiB scanned.
More from this repo
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 +...
recipes
Used when a user states a FinOps *outcome* rather than a tool.