BigQuery basics: datasets, tables, jobs
Create datasets and tables, run SQL queries, ingest data and manage BigQuery resources
- What
- Create datasets and tables, run SQL queries, ingest data and manage BigQuery resources
- Cost
- Free
- Needs
- a Google Cloud project with the BigQuery API enabled and billing configured (a monthly free query and storage quota exists); the gcloud and bq CLIs installed and authenticated. No API key is needed to install.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — Google's official BigQuery starter skill: enable the BigQuery API, create datasets and tables with JSON schemas, run standard SQL queries, manage datasets/tables/views and basic ingestion, with a reference library covering core concepts, change history, continuous queries, CLI usage, client libraries (Python/Java/Node/Go), the BigQuery remote MCP server and Terraform IaC, plus IAM & security guidance. By @google, listed here with credit to its creator. Honest caveats: requires a Google Cloud project with the BigQuery API enabled and billing configured (a monthly free query/storage quota exists, so costs are low for starters but not zero-free); every terminal `gcloud` invocation carries an inline usage-attribution tag — keep that prefix out of generated scripts and user-facing code as the skill instructs; for BigQuery AI/ML (forecast, anomaly detection, text generation) see the companion bigquery-ai-ml skill. Updated October 21, 2026 (version 1.0.2): the Attribution rule is stated in SKILL.md itself again, as a MUST READ — before any gcloud, REST API or MCP command, read references/attribution.md; the tag itself is unchanged (it identifies only the skill and its version, carries no user data, applies to direct terminal commands only, and an opt-out is documented). Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version: 1.0.2
Quick answer
BigQuery basics is a Google starter skill: enable the BigQuery API, create datasets and tables with JSON schemas, run SQL queries, manage datasets, tables and views, with a library covering concepts, change history and CLI usage, clients, MCP and Terraform, plus IAM and security guidance. It requires a Google Cloud project with billing configured, though a monthly free quota exists.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 18, 2026📌 Pinned version: commit a0c0862Before you start: tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead. Prerequisites: a Google Cloud project with the BigQuery API enabled and billing configured (a monthly free query and storage quota exists); the gcloud and bq CLIs installed and authenticated. No API key is needed to install. Install "BigQuery basics: datasets, tables, jobs" for me. It gives my agent Google's bigquery-basics contract: enable the BigQuery API, create datasets and tables from JSON schemas, run standard SQL queries with the bq CLI, do basic data ingestion, and manage BigQuery resources (datasets, tables, views, jobs). This prompt installs upstream version 1.0.2, as reviewed by Skill Harbor on October 21, 2026. Repository: https://raw.githubusercontent.com/google/skills/a0c086248586d2d12a433c95524a70aa6ebccf88/skills/cloud/bigquery-basics/SKILL.md (the skill is a whole folder: SKILL.md and the references/ folder, all under skills/cloud/bigquery-basics/ in the repository) Pinned version: install the code at commit a0c086248586d2d12a433c95524a70aa6ebccf88 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. Updated October 21, 2026: Skill Harbor regenerated this install prompt for bigquery-basics 1.0.2. What changed since 1.0.1, the version the previous prompt described: the Attribution section in SKILL.md is now a MUST READ and states the rule inline again. Before executing any gcloud, REST API, or MCP command, the agent MUST read references/attribution.md; and for commands executed directly in the terminal — never in generated scripts, Terraform, or user code — prefix gcloud with CLOUDSDK_METRICS_REQUEST_ATTRIBUTION="agent-skills/1.0 (skill:bigquery-basics)" and append agent-skills/1.0 (skill:bigquery-basics) to User-Agent headers. This is the same treatment as the other Google skills Skill Harbor regenerated: the tag identifies only the skill and its version and carries no user data, it must never be persisted with gcloud config set (that would mislabel unrelated later usage), and references/attribution.md documents a user opt-out — if I ask to disable attribution tagging, omit the variable and the User-Agent suffix. Correction to the previous prompt: it said SKILL.md itself no longer stated the tagging rule and only pointed to the reference — that is no longer accurate; 1.0.2 states the rule in SKILL.md itself, as an explicit MUST. Nothing else in what the skill does changed: setup, datasets, tables, queries and the reference library are the same. 1. Download the whole skill folder at the pinned commit into a temporary folder: SKILL.md and the references/ folder. 2. Compare SKILL.md with the fingerprint from Skill Harbor's review of October 21, 2026: - SKILL.md: SHA-256 56a16fab677f74728cc7f46aa8db5d2179be8cf6ad04b1582107dc3983d13db3, 3,452 bytes, 3,452 characters If it does not match, it changed since the review: do not install it yet — tell me what you found and let me decide. 3. Read the files and tell me in plain words: what the skill does when used, whether it connects to a service, whether it reads or sends any personal information or keys, and anything that seems unusual. Confirm in particular these points from the files: the skill works through my own authenticated gcloud and bq CLIs against my own Google Cloud project, so when I use it, my queries send my SQL and my data to BigQuery in that project — that happens when the skill is used, never during installation; the Attribution rule is mandatory in this version: before any gcloud, REST API or MCP command, read references/attribution.md, and for commands executed directly in the terminal, prefix gcloud with CLOUDSDK_METRICS_REQUEST_ATTRIBUTION="agent-skills/1.0 (skill:bigquery-basics)" set inline on each command and append agent-skills/1.0 (skill:bigquery-basics) to the User-Agent of direct API or MCP requests — the prefix belongs to direct terminal commands only, never in generated scripts, Terraform or code provided to me, and never persisted with gcloud config set; the tag identifies only the skill and its version and carries no user data, and I can opt out of that tagging as references/attribution.md documents; the repo contains no secrets in code, and credentials come only from my own gcloud authentication; and nothing is sent anywhere during installation — installing only downloads the files. 4. When I say yes, copy the whole folder into my skills folder, in a folder named "google-skills-bigquery-basics". 5. Check the copy opens correctly (valid frontmatter, skill name bigquery-basics, version 1.0.2, files in place) and tell me what was installed, where, and what is left for me to do (for example, enabling the BigQuery API in my Google Cloud project, and the related bigquery-ai-ml skill if I want the AI and ML capabilities). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Rules: only touch the temporary folder and the install target. Never ask me to paste secrets in chat: credentials go through the secure vault or environment variables. If something seems off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- a0c0862 · 2026-10-21
- Sandbox install test
- Install ran in our test sandbox · Nov 18, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.