bigquery-data-transfer-service

Name: bigquery-data-transfer-service
Availability: InStock
Author: aubreyhan

Discover BigQuery Data Transfer Service configurations and extract transfer metadata.

Updated Jun 10, 2026

Search Tags:#bigquery #data-ingestion #dts #transfer-configs #pipeline-discovery #oauth-authorization

Ready to run

npx skills add https://github.com/AubreyHan/SKILL_Repo --skill bigquery-data-transfer-service-aubreyhan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bigquery-data-transfer-service
Source: https://github.com/AubreyHan/SKILL_Repo/tree/main/bigquery-data-transfer-service
Command: npx skills add https://github.com/AubreyHan/SKILL_Repo --skill bigquery-data-transfer-service-aubreyhan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you discover, inspect, and validate BigQuery Data Transfer Service setups so you can avoid recreating existing ingestion pipelines and safely plan new ones.

Core Features & Use Cases

Transfer Discovery: Identify existing DTS transfer configs in a project and region before creating anything new.
Parameter Inspection: Inspect datasource requirements, authentication needs, and transfer metadata through the DTS REST API.
Pipeline Readiness: Validate whether a transfer is already running, disabled, or needs a manual run before proceeding.
Use Case: A data engineer can check whether Google Cloud Storage ingestion is already handled by DTS, confirm the exact configuration, and gather the parameters needed for a declarative deployment.

Quick Start

Ask the skill to inspect BigQuery Data Transfer Service transfers for the current project and region and report the exact datasource parameters needed to continue.

Frequently Asked Questions about bigquery-data-transfer-service

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I discover existing BigQuery Data Transfer Service configurations in my Google Cloud project?▼

To discover existing BigQuery Data Transfer Service configurations, this Skill inspects DTS transfer configs across specified Google Cloud projects and regions via the REST API, extracting transfer metadata and validating pipeline readiness before you create new setups.

How can I inspect BigQuery DTS parameters before setting up a new data ingestion pipeline?▼

You can inspect BigQuery DTS datasource requirements, authentication needs, and transfer metadata by requesting a parameter inspection through the DTS REST API, ensuring you validate existing transfers and confirm exact configurations before proceeding with new datasource setup.

Does validating BigQuery Data Transfer Service transfer configs require OAuth authorization?▼

Validating BigQuery Data Transfer Service transfer configs optionally requires OAuth authorization depending on the datasource, alongside REST API inspection and parameter validation to confirm assets and check whether transfers are running, disabled, or need a manual run.

What is the best way to check if a BigQuery DTS ingestion pipeline is already running or disabled?▼

The best way to check BigQuery DTS pipeline status is to perform a transfer discovery and readiness validation, which inspects existing transfer configs to report whether a transfer is currently running, disabled, or requires a manual run before proceeding.

Can I use BigQuery Data Transfer Service discovery to generate declarative deployment files for new data sources?▼

Yes, you can use BigQuery Data Transfer Service discovery to gather the exact datasource parameters needed for a declarative deployment, with the Skill confirming assets and validating configurations before generating a deployment.yaml file.

What are the limitations of using BigQuery DTS discovery for ingestion pipeline validation across regions?▼

BigQuery DTS discovery limitations include needing to specify exact Google Cloud projects and regions for REST API inspection, requiring optional OAuth authorization for certain datasources, and confirming assets manually before generating any deployment.yaml configurations.