agentleFS
jpantsjohajpantsjoha/googlecloud-plugin/skills/bigquery/SKILL.md

bigquery

Skill4 starsChanged 4 months agoMITView on GitHub

Query and manage data in Google BigQuery. Covers dataset and table management, IAM, cost-safe querying (dry-run first), partitioning, clustering, and bq CLI patterns. Always estimates cost before executing queries — BigQuery bills by bytes processed. Use when the user mentions: bigquery query, analytics on GCP, BigQuery IAM, BigQuery cost, bigquery partition, bigquery schema, sql on GCP.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use LIMIT in development; avoid SELECT * on multi-TB tables

    line 69

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

BigQuery

Serverless, highly scalable data warehouse. Bills per bytes processed — always dry-run before executing queries on large datasets.

Safety Rule — Dry-Run First

# Estimate bytes before executing — always do this on unknown datasets
bq query --dry_run --use_legacy_sql=false 'SELECT * FROM dataset.table'
# Output: "Query successfully validated. Assuming the tables are not modified,
# running this query will process X bytes."

Core Patterns

Create a dataset

bq mk --dataset \
  --location=REGION \
  --description="Description" \
  PROJECT_ID:DATASET_NAME

Run a query (with cost confirmation)

# 1. Dry-run first (see above)
# 2. Execute only after confirming cost
bq query --use_legacy_sql=false --location=REGION \
  'SELECT field FROM `project.dataset.table` LIMIT 100'

Grant dataset access (least-privilege)

bq show --format=prettyjson PROJECT_ID:DATASET > /tmp/ds.json
# Edit roles in /tmp/ds.json, then:
bq update --source /tmp/ds.json PROJECT_ID:DATASET

Create partitioned table (cost control)

CREATE TABLE dataset.table (
  event_date DATE,
  user_id STRING
)
PARTITION BY event_date
OPTIONS (partition_expiration_days = 365);

Cost Controls

  • Partition tables by date — queries on a partition scan only that partition
  • Cluster tables by high-cardinality filter columns
  • Set per-project quotas: IAM → Quotas → BigQuery — Query usage per day
  • Use LIMIT in development; avoid SELECT * on multi-TB tables

References

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.