gcp-pipeline-resource-provisioning
Automates declarative resource creation and provisioning for data pipelines, supporting BigQuery, Dataform, Dataproc, BigQuery Data Transfer Service (DTS), and other resources. It manages environment-specific configurations (dev, staging, prod) through a deployment.yaml file. Use when: - Modifying or creating deployment.yaml for deployment settings. - Resolving environment-specific variables (e.g., Project IDs, Regions) for deployment. - Provisioning supported infrastructure like BigQuery datasets/tables, Dataform resources, or DTS resources via deployment.yaml. Do not use when: - Resources already exist. - Managing resources not supported by `gcloud beta orchestration-pipelines resource-types list`. - Managing general cloud infrastructure (VMs, networks, Kubernetes, IAM policies), which are better suited for Terraform. - Infrastructure spans multiple cloud providers (AWS, Azure, etc.). - Already uses Terraform for the target resources.
Install
With your agent
Install OMGSkills skill "googlecloudplatform/data-agent-kit-plugin:skills/gcp-pipeline-resource-provisioning" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/GoogleCloudPlatform/data-agent-kit-plugin /tmp/data-agent-kit-plugin && ln -s /tmp/data-agent-kit-plugin/skills/gcp-pipeline-resource-provisioning ~/.claude/skills/gcp-pipeline-resource-provisioningFrom README
How to use this skill Create or update existing deployment.yaml file and deploy resources. All configuration files MUST be maintained together in the repository root. Mandatory labels [!IMPORTANT] Whenever you generate resource definitions in deployment.yaml, you MUST directly populate the datacloud label under definition.labels for every resource to track the source of creation. Determine the value based on your current IDE environment: For Antigravity, set datacloud: "antigravity" For VS Code, set datacloud: "vscode" For any other environment, set datacloud: "other" Do not use a variable substitution for this label; hardcode the appropriate string value directly into each resource definition (e.g., replacing REQUIREDLABEL placeholders). Special rule for BigQuery DTS Ingestion: Whenever you generate a bigquerydatatransfer.transferConfig in deployment.yaml, you MUST also explicitly define its target destination bigquery.dataset in the same file and apply the datacloud label to it.
More from this repo
accidental-data-loss-prevention
**STOP AND VERIFY**: Before running any command or tool that results in irreversible data loss, you MUST obtain...
bigquery-ai-ml
Leverages BigQuery's built-in machine learning and GenAI capabilities for advanced data analytics.
bigquery-bigframes
Generates Python code using BigQuery DataFrames (BigFrames).