write-bigquery-dq-tests

write-bigquery-dq-tests is a skill for Claude Code from orchestra-hq/orchestra-skills. It costs 38 tokens per session (354 once invoked), scanned A, original, MIT.

A workflow for checking BigQuery data and building a data-quality test pipeline in Orchestra. BigQuery is Google's hosted service for storing and querying large datasets, while data-quality tests check whether data meets defined expectations.

In plain words
What is it for?
Use it to inspect BigQuery tables, write suitable GoogleSQL checks, deploy and run an Orchestra pipeline, and report the findings.
Why use it?
It avoids relying on generic checks that may not fit the meaning of each column. It profiles the data first, then uses the results to create checks, run them, and report real failures.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the orchestra plugin — 19 skills, 1 hook shipped together

Good fit Use it to inspect BigQuery tables, write suitable GoogleSQL checks, deploy and run an Orchestra pipeline, and report the findings.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/orchestra-hq/orchestra-skills/write-bigquery-dq-tests
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add orchestra-hq/orchestra-skills --skill write-bigquery-dq-tests
Clone the repo
git clone --depth 1 https://github.com/orchestra-hq/orchestra-skills

Made for: Claude Code.

Or install orchestra, the plugin that ships this one along with the rest of its 19 skills, 1 hook.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for write-bigquery-dq-tests

README.md
[![agentmods](https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/write-bigquery-dq-tests/github.svg)](https://agentmods.dev/skills/orchestra-hq/orchestra-skills/write-bigquery-dq-tests)
Your own site
<a href="https://agentmods.dev/skills/orchestra-hq/orchestra-skills/write-bigquery-dq-tests"><img src="https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/write-bigquery-dq-tests/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for write-bigquery-dq-tests

Your own site · 80×15
<a href="https://agentmods.dev/skills/orchestra-hq/orchestra-skills/write-bigquery-dq-tests"><img src="https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/write-bigquery-dq-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 354 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00038 $0.00354
Opus 5.5 $0.00015 $0.00142
Sonnet 5.5 $0.00008 $0.00071
Haiku 4.5 $0.00004 $0.00035

Measured 1mo ago against content hash 31f0d49fcf8f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

write-bigquery-dq-tests scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/orchestra/skills/write-bigquery-dq-tests/SKILL.md · 30 lines

What it actually says

Goal: inspect real BigQuery data, design tests that fit what each column means (not a generic null check on everything), deploy them as an Orchestra pipeline, run it, and report what's actually wrong. A test that fails because the data is bad is the skill working correctly — do not tune thresholds until everything is green.

Flow: profile → design tests → write pipeline YAML → branch (or create pipeline if no git) → register → run → report.

Read first

  • ../../references/orchestra/dq-tests/bigquery.md — BigQuery profiling SQL, the test catalogue in GoogleSQL, the pipeline YAML, and BigQuery-specific error causes.
  • ../../references/orchestra/dq-tests/workflow.md — the engine-agnostic rest of the workflow: thresholds, the matrix/gating pattern, branching, registering, triggering, and how to interpret results. Applies unchanged to BigQuery.

Workflow

  1. Profile the data and design tests per bigquery.md §1–2.
  2. Write the pipeline YAML per bigquery.md §3, following the gating pattern and threshold rules in workflow.md.
  3. Branch the repo (or create the pipeline if there's no git), register, trigger, poll, and report — all per workflow.md, using the BigQuery-specific error causes and qualified-name format from bigquery.md §4 when interpreting results.
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 30 lines · 38 tokens per session scan A 31f0d49fcf8f

Subscribe to this mod's changes

write-bigquery-dq-tests is a skill published in the GitHub repository orchestra-hq/orchestra-skills (9 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 354 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-09.

Related

Other skills, from other repositories

review-prs

Review a GitHub pull request in the googleapis/mcp-toolbox repo against the team's reviewer checklist: PR title/description conventions, linked issue, logic errors and unhandled edge cases, breaking changes, test coverage, docs updates, security (input handling), and new dependencies. Use whenever a maintainer asks…

googleapis/mcp-toolbox · 162 tokens

fix-failing-tests

Diagnose a failing test in the googleapis/mcp-toolbox repo and land a fix by reasoning from the actual error: read the failure, reproduce it, shrink it until the cause is forced into the open, then fix the cause. Use this whenever a test or CI job is red, a build breaks after a change, many packages fail at once, or a…

googleapis/mcp-toolbox · 87 tokens

reproduce-bug

Reproduce a reported bug in googleapis/mcp-toolbox and decide whether it is real, delivering an evidence-backed verdict: confirmed, already fixed, misconfiguration, client-side, works as intended, not reproducible, or blocked. Use whenever a maintainer asks you to reproduce, verify, confirm, or investigate a bug…

googleapis/mcp-toolbox · 130 tokens

azure-cosmos-db-py

Build Azure Cosmos DB NoSQL services with Python/FastAPI following production-grade patterns. Use when implementing database client setup with dual auth (DefaultAzureCredential + emulator), service layer classes with CRUD operations, partition key strategies, parameterized queries, or TDD patterns for Cosmos. Triggers…

microsoft/skills · 96 tokens

Drizzle ORM Testing

Testing patterns for Drizzle ORM covering migration testing, query builder testing, transaction testing, and database integration testing with PostgreSQL, SQLite, and MySQL.

PramodDutta/qaskills · 36 tokens

finance-weekly-outlook

Generate a source-backed weekly financial trading outlook from daily-finance, finance-core-analysis, and finance-explosive-article outputs plus fresh authoritative market data. Use when the user asks for future-one-week market outlook, weekly bullish/bearish sectors, stock picks, China A-share and US stock coverage…

digoal/blog · 122 tokens