Agent skill · data analytics · google
bigquery-bigframes
Generates Python code using BigQuery DataFrames (BigFrames). Use by default for any Python data task involving BigQuery, including data processing, analysis, and machine learning. Don't use for SQL-first workflows or the google-cloud-bigquery client library — use bigquery-basics.
Why this skill is useful
Provides domain-specific best practices and optimization techniques for using BigFrames with BigQuery that the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-06. 15,831 stars on the source repository.
What this skill does
BigFrames (BigQuery DataFrame) basics BigFrames is a Python library that lets you take advantage of BigQuery data processing by using familiar Python APIs. Attribution MUST READ: Before executing any gcloud, REST API, or MCP command, you MUST read Usage Attribution. For commands executed directly in the terminal (never in generated scripts, Terraform, or user code), prefix gcloud with CLOUDSDKMETRICSREQUESTATTRIBUTION="agent-skills/1.0 (skill:bigquery-bigframes)" and append agent-skills/1.0 (skill:bigquery-bigframes) to User-Agent headers. Dataframe API best practices Stay in the Cloud: Perform data cleaning, transformation, and analysis via BigFrames methods to leverage BigQuery's scale rather than downloading data. Prefer partial ordering mode: Enable partial ordering mode right after importing BigFrames. This speeds up data processing significantly by relaxing row-sequence constraints. Use peek() for data preview: Use peek(n) to preview data instead of head(n). peek(n) randomly samples n rows and is significantly faster. head(n) returns rows in strict order and fails in partial ordering mode unless the DataFrame has been explicitly sorted. Avoid materializing data locally: Methods like topandas() download all data to client memory, bypassing BigQuery’s distributed computation and risking Out of Memory (OOM) errors. Do not materialize data locally unless: The dataset is small enough to fit safely in memory. An error message explicitly requires local materialization. Prefer Dataframe API over SQL queries: Do not write raw SQL queries via readgbq() if a DataFrame/Series method achieves the same result, as it breaks the Pandas abstraction and prevents lazy query execution. Accessors over UDFs/Lambdas: Use built-in accessors (e.g., df.col.str., df.col.dt.) instead of remote User Defined Functions (UDFs). UDFs require extra resources and time to deploy. Do not use lambdas with Series.map() or DataFrame.apply(). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills google/bigquery-bigframes