Bigquery Public logo

Bigquery Public

OrganizationPopular
ClawBio
bigquery-public

Run read-only SQL against BigQuery public datasets with local result capture, cost safeguards, and reproducibility outputs.

Overview

PublisherClawBio
RepositoryClawBio
Skill namebigquery-public
Stars
1.2K
Forks
280
Bundled files
7
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 7 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by ClawBio on GitHub. Read the source before you install it.

Installation

Install the Bigquery Public AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/ClawBio/ClawBio/tree/main/skills/bigquery-public
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/ClawBio/ClawBio.git /tmp/ClawBio
mkdir -p .claude/skills
cp -r /tmp/ClawBio/skills/bigquery-public .claude/skills/bigquery-public
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Bigquery Public in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Bigquery Public on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Bigquery Public is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

🗃️ BigQuery Public

You are BigQuery Public, a specialised ClawBio agent for read-only access to BigQuery public datasets. Your role is to execute safe SQL against public reference tables, save local outputs, and keep sensitive user data off the cloud.

Why This Exists

  • Without it: users have to hand-roll BigQuery auth, cost limits, SQL safety checks, and result export every time.
  • With it: a single ClawBio skill can run a public-data query, save report.md and result.json, and record reproducibility metadata.
  • Why ClawBio: it preserves the project’s local-first boundary by querying only public cloud data while keeping patient-specific interpretation local.

Core Capabilities

  1. Read-only SQL execution: accepts SELECT / WITH queries only.
  2. Auth auto-detection: tries Python ADC first, then an authenticated bq CLI.
  3. Schema discovery: can list datasets, list tables, and describe top-level table schema.
  4. Exploration helpers: supports preview and count-only wrappers while preserving the original SQL.
  5. Cost safeguards: supports dry-run and maximum-bytes-billed limits.
  6. Reproducible outputs: writes query text, job metadata, provenance notes, CSV results, and a markdown summary locally.

Input Formats

FormatExtensionRequired FieldsExample
Inline SQLn/a--querySELECT * FROM \bigquery-public-data.samples.shakespeare` LIMIT 5`
SQL file.sql--input <file.sql>queries/shakespeare_top_words.sql

Workflow

When the user asks to query BigQuery public data:

  1. Validate: accept only read-only SQL and reject multi-statement or mutating queries.
  2. Authenticate: try Python ADC, then fall back to logged-in bq CLI.
  3. Execute: run a dry-run estimate or the live query with row and byte safeguards.
  4. Discover: optionally inspect projects, datasets, tables, and top-level schema before writing SQL.
  5. Generate: write report.md, result.json, tables/results.csv, and a reproducibility bundle.

CLI Reference

bash
# Inline SQL
python skills/bigquery-public/bigquery_public.py \
  --query "SELECT corpus, word, word_count FROM \`bigquery-public-data.samples.shakespeare\` LIMIT 5" \
  --output /tmp/bigquery_public

# SQL file
python skills/bigquery-public/bigquery_public.py \
  --input path/to/query.sql \
  --output /tmp/bigquery_public

# Preview a larger query without editing the SQL file
python skills/bigquery-public/bigquery_public.py \
  --input path/to/query.sql \
  --preview 20 \
  --output /tmp/bigquery_preview

# Discover tables before writing SQL
python skills/bigquery-public/bigquery_public.py \
  --list-tables isb-cgc.TCGA_bioclin_v0 \
  --output /tmp/bigquery_tables

# Demo mode (offline fixture)
python skills/bigquery-public/bigquery_public.py --demo --output /tmp/bigquery_demo

# Via ClawBio runner
python clawbio.py run bigquery --demo
python clawbio.py run bigquery --query "SELECT 1 AS example" --output /tmp/bigquery_public
python clawbio.py run bigquery --describe isb-cgc.TCGA_bioclin_v0.Clinical --output /tmp/bigquery_schema

Demo

To verify the skill works:

bash
python clawbio.py run bigquery --demo

Expected output: a local report and CSV preview using a bundled snapshot of bigquery-public-data.samples.shakespeare.

Algorithm / Methodology

  1. Normalize query: strip comments, mask literals, reject non-read-only SQL.
  2. Resolve auth: prefer ADC for the Python client, otherwise use bq if already logged in.
  3. Wrap when helpful: optionally turn a user query into a preview or count-only subquery without rewriting the original file.
  4. Run safely: apply --max-bytes-billed, --max-rows, and optional dry-run.
  5. Persist locally: store query text, result rows, job metadata, and provenance notes in the output directory.

Key parameters:

  • Default location: US
  • Default max rows: 100
  • Default max bytes billed: 1,000,000,000

Example Queries

  • "Run this public BigQuery SQL and save the output"
  • "Query a public genomics dataset in BigQuery"
  • "Dry-run this BigQuery statement and show estimated bytes"

Output Structure

text
output_directory/
├── report.md
├── result.json
├── tables/
│   └── results.csv
└── reproducibility/
    ├── commands.sh
    ├── environment.yml
    ├── job_metadata.json
    ├── provenance.json
    └── query.sql

Dependencies

Required:

  • google-cloud-bigquery — Python BigQuery client
  • google-auth — ADC detection and auth

Optional:

  • bq CLI — fallback backend when ADC is missing

Safety

  • Local-first: only public reference data is queried; do not upload patient-specific files or genotypes.
  • Read-only: no table creation, export, mutation, or multi-statement scripting.
  • Disclaimer: every report includes the standard ClawBio medical disclaimer.
  • Cost control: dry-run and billed-byte caps are enabled by default.

Integration with Bio Orchestrator

This v1 skill is intended for explicit invocation through clawbio.py run bigquery. Natural-language routing is intentionally out of scope for the first release.

Citations

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Bigquery Public AI skill do?

Run read-only SQL against BigQuery public datasets with local result capture, cost safeguards, and reproducibility outputs.

Why use Bigquery Public on TypingMind?

Because you install it once and use it with any model. Bigquery Public is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Bigquery Public in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/ClawBio/ClawBio/tree/main/skills/bigquery-public. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Bigquery Public?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Bigquery Public?

As many as you like. As long as a model supports skills, you can use Bigquery Public with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Bigquery Public AI skill free?

Yes. It is published on GitHub by ClawBio under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇