How do I install the Dcx Bigquery skill?

Run npx skillmds@latest add haiyuan-eng-google/dcx-bigquery in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Dcx Bigquery safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Dcx Bigquery?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Dcx Bigquery free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Dcx Bigquery?

haiyuan-eng-google (@haiyuan-eng-google) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Dcx Bigquery by haiyuan-eng-google — Agent Skill

Name: Dcx Bigquery
Author: haiyuan-eng-google

File contents

When to use this skill

Use when the user wants to:

Set up dcx authentication or understand global flags
Run SQL queries against BigQuery
Inspect table or view schemas
Discover BigQuery connections
Understand dcx output formats

Authentication

dcx resolves credentials in order (first match wins):

--token flag or DCX_TOKEN env var
--credentials-file flag or DCX_CREDENTIALS_FILE env var
Stored credentials from dcx auth login (OAuth browser flow)
GOOGLE_APPLICATION_CREDENTIALS env var
Default ADC (gcloud auth application-default login or GCE metadata)

dcx auth login      # opens browser for Google OAuth
dcx auth status     # shows active credential source
dcx auth logout     # clears stored credentials

Global flags

Flag	Env var	Default	Required
`--project-id`	`DCX_PROJECT`	—	Yes (all commands)
`--dataset-id`	`DCX_DATASET`	—	Analytics commands only
`--location`	`DCX_LOCATION`	`US`	No
`--format`	—	`json`	No
`--token`	`DCX_TOKEN`	—	No
`--credentials-file`	`DCX_CREDENTIALS_FILE`	—	No

Output formats

Format	Best for
`--format json`	Automation, piping to `jq`, CI
`--format table`	Visual scanning in terminal
`--format text`	Demos, human-readable summaries

SQL queries

dcx jobs query --project-id my-proj --query "SELECT COUNT(*) FROM \`my-proj.ds.table\`" --format table
dcx jobs query --project-id my-proj --query "SELECT 1" --dry-run

--dry-run shows the API request without executing
--use-legacy-sql enables legacy SQL dialect (default: standard SQL)
Does not require --dataset-id

Schema inspection

# Table metadata (includes schema.fields)
dcx tables get --project-id P --dataset-id D --table-id T --format json

# INFORMATION_SCHEMA query
dcx jobs query --project-id P \
  --query "SELECT column_name, data_type FROM \`P.D\`.INFORMATION_SCHEMA.COLUMNS WHERE table_name = 'T'" \
  --format table

Connections

BigQuery connections are inspected via INFORMATION_SCHEMA queries:

dcx jobs query --project-id P \
  --query "SELECT routine_name, remote_function_info FROM \`P.D\`.INFORMATION_SCHEMA.ROUTINES WHERE remote_function_info IS NOT NULL" \
  --format table

Decision rules

Use dcx jobs query for direct SQL execution
Use dcx tables get for single-table schema inspection
Use INFORMATION_SCHEMA for cross-table schema queries
Use --dry-run to verify without executing
jobs query does not require --dataset-id; analytics commands do

Constraints

TIMESTAMP values are auto-converted from epoch to ISO 8601
Long-running queries are polled automatically
Connection management (create/delete) requires BigQuery Connection API directly

References

See dcx-bigquery-api for Discovery-generated dataset/table/routine/model commands
See dcx-analytics for agent analytics workflows
See dcx-ca for natural language queries

---name: dcx-bigquerydescription: BigQuery router skill — authentication, global flags, SQL queries, schema inspection, and connections. Entry point for all BigQuery-specific dcx usage.---## When to use this skillUse when the user wants to:- Set up dcx authentication or understand global flags- Run SQL queries against BigQuery- Inspect table or view schemas- Discover BigQuery connections- Understand dcx output formats## Authenticationdcx resolves credentials in order (first match wins):1. `--token` flag or `DCX_TOKEN` env var2. `--credentials-file` flag or `DCX_CREDENTIALS_FILE` env var3. Stored credentials from `dcx auth login` (OAuth browser flow)4. `GOOGLE_APPLICATION_CREDENTIALS` env var5. Default ADC (`gcloud auth application-default login` or GCE metadata)```bashdcx auth login # opens browser for Google OAuthdcx auth status # shows active credential sourcedcx auth logout # clears stored credentials```## Global flags| Flag | Env var | Default | Required ||------|---------|---------|----------|| `--project-id` | `DCX_PROJECT` | — | Yes (all commands) || `--dataset-id` | `DCX_DATASET` | — | Analytics commands only || `--location` | `DCX_LOCATION` | `US` | No || `--format` | — | `json` | No || `--token` | `DCX_TOKEN` | — | No || `--credentials-file` | `DCX_CREDENTIALS_FILE` | — | No |## Output formats| Format | Best for ||--------|----------|| `--format json` | Automation, piping to `jq`, CI || `--format table` | Visual scanning in terminal || `--format text` | Demos, human-readable summaries |## SQL queries```bashdcx jobs query --project-id my-proj --query "SELECT COUNT(*) FROM \`my-proj.ds.table\`" --format tabledcx jobs query --project-id my-proj --query "SELECT 1" --dry-run```- `--dry-run` shows the API request without executing- `--use-legacy-sql` enables legacy SQL dialect (default: standard SQL)- Does **not** require `--dataset-id`## Schema inspection```bash# Table metadata (includes schema.fields)dcx tables get --project-id P --dataset-id D --table-id T --format json# INFORMATION_SCHEMA querydcx jobs query --project-id P \ --query "SELECT column_name, data_type FROM \`P.D\`.INFORMATION_SCHEMA.COLUMNS WHERE table_name = 'T'" \ --format table```## ConnectionsBigQuery connections are inspected via INFORMATION_SCHEMA queries:```bashdcx jobs query --project-id P \ --query "SELECT routine_name, remote_function_info FROM \`P.D\`.INFORMATION_SCHEMA.ROUTINES WHERE remote_function_info IS NOT NULL" \ --format table```## Decision rules- Use `dcx jobs query` for direct SQL execution- Use `dcx tables get` for single-table schema inspection- Use INFORMATION_SCHEMA for cross-table schema queries- Use `--dry-run` to verify without executing- `jobs query` does not require `--dataset-id`; analytics commands do## Constraints- TIMESTAMP values are auto-converted from epoch to ISO 8601- Long-running queries are polled automatically- Connection management (create/delete) requires BigQuery Connection API directly## References- See **dcx-bigquery-api** for Discovery-generated dataset/table/routine/model commands- See **dcx-analytics** for agent analytics workflows- See **dcx-ca** for natural language queries

Frequently asked questions

Dcx Bigquery