BigQuery Partitioned Table Creation

---
name: bigquery-partitioned-table-creation
description: "Inspect a BigQuery dataset and create one approved partitioned or clustered table."
---

# BigQuery Partitioned Table Creation

Inspect a BigQuery dataset and create one approved partitioned or clustered table.

## Required Aident Actions

- <action-tag>composio:googlebigquery_tools:googlebigquery_get_dataset</action-tag> (required inputs: project_id, dataset_id): Tool to retrieve BigQuery dataset metadata including location via the datasets.get API. Use this before creating jobs/queries if the workflow has been failing with location mismatch to confirm the dataset's region...
- <action-tag>composio:googlebigquery_tools:googlebigquery_create_table</action-tag> (required inputs: project_id, dataset_id, tableReference): Tool to create a new, empty table in a BigQuery dataset. Use when setting up data infrastructure for standard tables, external tables, views, or materialized views. Supports partitioning, clustering, and encryption...
- <action-tag>composio:googlebigquery_tools:googlebigquery_get_table_schema</action-tag> (required inputs: project_id, dataset_id, table_id): Tool to fetch a BigQuery table's schema and metadata without querying row data. Use before generating SQL queries to avoid column name typos and confirm field types and nullable modes. This is especially useful when...

Use Aident Loadout to read the current Action schema before constructing inputs. Check the required integration connection in Aident Vault. If an Action is billable or mutating, run Aident preflight, show the affected target and quoted cost or risk, and wait for explicit user confirmation before execution.

## Workflow

1. Confirm the requested outcome, source material, destination, audience, constraints, and acceptance criteria.
2. Apply the source-derived guidance below to create a concrete plan. Resolve ambiguity before invoking an Action.
3. Select only the Aident Actions whose documented effect directly advances the requested outcome. Do not invoke every listed Action by default.
4. Inspect the current schema and prepare the minimum valid input for each selected Action.
5. Preflight each selected Action. Execute it only after any required confirmation, in dependency order, and carry returned IDs or asset URLs into later steps.
6. Verify the returned IDs, URLs, statuses, or artifacts against the acceptance criteria. Report partial completion precisely and do not repeat paid or mutating calls blindly.

## Source-Derived Guidance

- Verify dataset location and design schema, partitioning, clustering, and encryption before creation.
- Read back the created schema and report the canonical table identifier.

## Execution Boundaries

- Treat upstream provider-specific commands as background knowledge only. Execute the workflow through the exact Aident Actions above.
- Never request raw credentials in chat. Use Aident Vault connection flows for required accounts.
- Preserve user-provided wording, brand constraints, rights restrictions, and target identifiers. Do not invent authorization.
- Read current state before a mutation, state the exact target, and include a rollback or recovery step in the result.
- Stop when a required integration is disconnected, preflight rejects the input, the target is ambiguous, or the user declines a required confirmation.

## Output

Return the execution plan, selected Action names, confirmed targets, Aident result identifiers or asset URLs, verification evidence, and any remaining blocked step.

## Attribution

This Skill adapts the reviewed upstream workflow. See [UPSTREAM.md](UPSTREAM.md) for the pinned source and [LICENSE.txt](LICENSE.txt) for the preserved license.