bigquery
Inspect BigQuery Schemas with the bq CLI
BigQuery exploration can expose sensitive data or consume excessive resources. This skill provides cautious bq patterns for schema inspection, table discovery, row counts, and cost checks.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "bigquery" from https://skillstore.io/skills/bfdcampos-bigquery.md and its manifest at https://skillstore.io/api/skills/bfdcampos-bigquery/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "bigquery". Inspect the schema for the orders table without reading customer rows.
Expected outcome:
A metadata-only plan identifies the required project and dataset, retrieves ordered column names and types, and avoids table content.
Using "bigquery". Find tables containing payment in their names.
Expected outcome:
A table-discovery response searches INFORMATION_SCHEMA, sorts matching names, and asks for the project and dataset before execution.
Using "bigquery". Estimate the impact of an expensive query.
Expected outcome:
A cautious response recommends a dry run, reviews bytes processed, verifies permissions, and requests approval before the full query.
Security Audit
Medium RiskAll 81 Ruby or shell backtick alerts are false positives caused by Markdown and BigQuery identifier syntax, and both reconnaissance alerts are benign guidance. Two fixed /tmp writes remain confirmed, while semantic review found overbroad metadata authorization and disclosure of organization-specific cloud identifiers.
Confirmed security concerns (2)
Capability review items (2)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
โ๏ธ External commands (50)
๐ Filesystem access (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/bfdcampos-bigquery/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/bfdcampos-bigquery?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/bfdcampos-bigquery?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/bfdcampos-bigquery/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/bfdcampos-bigquery.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
BfdCampos. (2026). bigquery security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/bfdcampos-bigquery/audits/9BibTeX citation
@techreport{bfdcampos-bfdcampos-bigquery-2026,
author = {BfdCampos},
title = {bigquery security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/bfdcampos-bigquery/audits/9},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "bigquery security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
- name: "BfdCampos"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/bfdcampos-bigquery/audits/9"
identifiers:
- type: other
value: "skillstore:bfdcampos-bigquery:audit:9"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Inspect source schemas
Review column names and types before creating or updating dbt source models.
Discover warehouse tables
Find relevant tables by name while avoiding access to stored row content.
Investigate pipeline failures
Verify source existence, schema changes, and table size before deeper debugging.
Try These Prompts
Show how to inspect columns and types for [PROJECT].[DATASET].[TABLE] using Standard SQL. Do not query table rows.
Create a bq command that lists tables in [PROJECT].[DATASET] matching [PATTERN]. Explain placeholders and keep the query metadata-only.
Help diagnose this BigQuery or dbt error: [ERROR]. Verify table existence and schema, then suggest the least invasive next check.
Design a cautious investigation for [DATA_ISSUE] in [PROJECT].[DATASET]. Include permission checks, cost estimation, metadata queries, and approval before sampling rows.
Best Practices
- Confirm the project, dataset, permissions, and data classification before running any query.
- Start with INFORMATION_SCHEMA, row counts, and dry runs before accessing table contents.
- Use fully qualified identifiers, Standard SQL, explicit limits, and approved output destinations.
Avoid
- Do not query PII, employee, credential, or financial rows without explicit authorization.
- Do not treat metadata access as universally safe or free.
- Do not write query results to predictable shared temporary paths.