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
- G1Joshi/Agent-Skillstheir own version, first seen Oct 13, 2026
- presmihaylov/skillstheir own version, first seen Mar 5, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- G1Joshi/Agent-Skills★ 15same name
- presmihaylov/skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- agent-architectSkill
- cloud-runSkill
- cloud-storageSkill
- gcloud-guardrailsSkill
- gcp-architectSkill
- gcp-opsSkill
- gcp-project-contextSkill
- gcp-qaSkill
- gcp-securitySkill
- gkeSkill
- google-skills-catalogSkill
- iamSkill
- logging-monitoringSkill
- mcp-serversSkill
- networkingSkill
- solution-designerSkill
- terraform-gcpSkill
- vertex-aiSkill
- well-architectedSkill
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
- Very specific: line 69
Use LIMIT in development; avoid SELECT * on multi-TB tables
≈ “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.
Files
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_NAMERun 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:DATASETCreate 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
LIMITin development; avoidSELECT *on multi-TB tables
References
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
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.

