# Bigquery troubleshooting

> Bigquery troubleshooting is an open-source agent skill for databases. Provides diagnostic workflows and step-by-step root-cause analysis procedures for actively broken, failing, or slow BigQuery jobs, execution. It is available on Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose.

- **Kind:** Skill
- **Pricing:** Open source
- **Platforms:** Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf, Goose
- **Website:** https://github.com/google/skills/tree/main/skills/cloud/bigquery-troubleshooting
- **Repository:** https://github.com/google/skills
- **GitHub stars:** 24,379
- **License:** Apache-2.0
- **Skill name:** bigquery-troubleshooting
- **Collection:** https://github.com/google/skills
- **Categories:** databases
- **Listing updated:** 2026-11-17

## About

Provides diagnostic workflows and step-by-step root-cause analysis procedures for actively broken, failing, or slow BigQuery jobs, execution graph and query plan stage bottlenecks, system performance issues, or unexpectedly expensive workloads. Use when interpreting symptoms, isolating bottlenecks, diagnosing cost spikes (on-demand query spend, capacity slot autoscaling, storage growth), execution graph stages or substep variables, identifying root causes, and determining remediation steps. Don't use for writing or optimizing SQL, proactive capacity planning, or storage layout design (use bigquery-optimization), or when the user already knows which telemetry they want and just needs the query (use bigquery-observability).

## When your agent uses it

> Provides diagnostic workflows and step-by-step root-cause analysis procedures for actively broken, failing, or slow BigQuery jobs, execution graph and query plan stage bottlenecks, system performance issues, or unexpectedly expensive workloads. Use when interpreting symptoms, isolating bottlenecks, diagnosing cost spikes (on-demand query spend, capacity slot autoscaling, storage growth), execution graph stages or substep variables, identifying root causes, and determining remediation steps. Don't use for writing or optimizing SQL, proactive capacity planning, or storage layout design (use bigquery-optimization), or when the user already knows which telemetry they want and just needs the query (use bigquery-observability).

## What it can access

From a static check of the files on GitHub; nothing was run.

- [Instructions only, no scripts](https://github.com/google/skills/tree/HEAD/skills/cloud/bigquery-troubleshooting)
- [License: Apache-2.0](https://github.com/google/skills/tree/HEAD/skills/cloud/bigquery-troubleshooting)

## Install

### Claude Code

Copy the skill folder to `~/.claude/skills/bigquery-troubleshooting` to use it in all your projects:

```sh
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/google/skills.git "$tmp" &&
mkdir -p ~/.claude/skills &&
rm -rf ~/.claude/skills/bigquery-troubleshooting &&
cp -R "$tmp/skills/cloud/bigquery-troubleshooting" ~/.claude/skills/bigquery-troubleshooting &&
rm -rf "$tmp"
```

For one project only, put the folder in `.claude/skills/bigquery-troubleshooting` inside it instead.

### Codex

Copy the skill folder to `~/.agents/skills/bigquery-troubleshooting` to use it in every repository:

```sh
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/google/skills.git "$tmp" &&
mkdir -p ~/.agents/skills &&
rm -rf ~/.agents/skills/bigquery-troubleshooting &&
cp -R "$tmp/skills/cloud/bigquery-troubleshooting" ~/.agents/skills/bigquery-troubleshooting &&
rm -rf "$tmp"
```

For one repository only, put the folder in `.agents/skills/bigquery-troubleshooting` inside it instead.

### Cursor

Copy the skill folder to `~/.cursor/skills/bigquery-troubleshooting` to use it in every project:

```sh
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/google/skills.git "$tmp" &&
mkdir -p ~/.cursor/skills &&
rm -rf ~/.cursor/skills/bigquery-troubleshooting &&
cp -R "$tmp/skills/cloud/bigquery-troubleshooting" ~/.cursor/skills/bigquery-troubleshooting &&
rm -rf "$tmp"
```

For one project only, put the folder in `.cursor/skills/bigquery-troubleshooting` inside it instead.

### Gemini CLI

Run in a terminal (add `--scope workspace` to install it for the current workspace only):

```sh
gemini skills install https://github.com/google/skills.git --path skills/cloud/bigquery-troubleshooting
```

Or copy the folder to `~/.gemini/skills/bigquery-troubleshooting` yourself.

### VS Code

For GitHub Copilot in VS Code, copy the skill folder to `~/.copilot/skills/bigquery-troubleshooting`:

```sh
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/google/skills.git "$tmp" &&
mkdir -p ~/.copilot/skills &&
rm -rf ~/.copilot/skills/bigquery-troubleshooting &&
cp -R "$tmp/skills/cloud/bigquery-troubleshooting" ~/.copilot/skills/bigquery-troubleshooting &&
rm -rf "$tmp"
```

For one project only, put the folder in `.github/skills/bigquery-troubleshooting` inside it instead.

### Other agents

Get the folder:

```sh
git clone --depth 1 https://github.com/google/skills.git
```

Then copy `skills/skills/cloud/bigquery-troubleshooting` into your agent's skills folder as `bigquery-troubleshooting`. Agents that support SKILL.md read one folder per skill.

## FAQ

### How do I install Bigquery troubleshooting in Claude Code?

Copy the skill folder from GitHub to ~/.claude/skills/bigquery-troubleshooting to use it in all your projects, or to .claude/skills/bigquery-troubleshooting in one project.

### Does Bigquery troubleshooting run scripts?

No. It is instructions only, with no scripts. This comes from a static check of the files on GitHub; nothing was run. Read the files before you install it.

### Which AI agents can use Bigquery troubleshooting?

Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose. Each reads skills in the SKILL.md format from its own folder; the install steps on this page list them.

### What are the best alternatives to Bigquery troubleshooting?

The closest alternatives to Bigquery troubleshooting are Bigquery pipeline audit, SQL server table reconciliation, Postgresql optimization, Pinecone rag and Supabase rls policies.

## Alternatives

- [Bigquery pipeline audit](https://ai-powered.com/skills/bigquery-pipeline-audit): Bigquery pipeline audit is an open-source agent skill for databases.
- [SQL server table reconciliation](https://ai-powered.com/skills/sql-server-table-reconciliation): SQL server table reconciliation is an open-source agent skill for databases.
- [Postgresql optimization](https://ai-powered.com/skills/postgresql-optimization): Postgresql optimization is an open-source agent skill for databases.
- [Pinecone rag](https://ai-powered.com/skills/pinecone-rag): Pinecone rag is an open-source agent skill for knowledge and memory.
- [Supabase rls policies](https://ai-powered.com/skills/supabase-rls-policies): Supabase rls policies is an open-source agent skill for databases.
- [Snowflake semanticview](https://ai-powered.com/skills/snowflake-semanticview): Snowflake semanticview is an open-source agent skill for databases.
- [Creating oracle to postgres migration integration tests](https://ai-powered.com/skills/creating-oracle-to-postgres-migration-integration-tests): Creating oracle to postgres migration integration tests is an open-source agent skill for databases.
- [Migrating oracle to postgres data access code](https://ai-powered.com/skills/migrating-oracle-to-postgres-data-access-code): Migrating oracle to postgres data access code is an open-source agent skill for databases.

---
Source: https://ai-powered.com/skills/bigquery-troubleshooting
