Agent skill · data analytics · google

datalineage-bigquery-asset-impact-analysis

Analyzes the downstream impact (blast radius) using data lineage on Google Cloud when a BigQuery table or view is broken, stale, or modified. Identifies all downstream tables, dashboards, and processes that will be affected. Use when: - Performing a blast radius or impact analysis for a BigQuery table or view. - Assessing the consequences of modifying, deleting, or pausing updates to a BigQuery asset. - Identifying downstream dependencies (tables, dashboards, processes) of a BigQuery asset. Don't use for: - General BigQuery querying or data analysis (use BigQuery-related tools instead). - Non-BigQuery assets (e.g., Cloud Storage files) unless they are part of the BigQuery lineage. - Creating or modifying lineage links directly.

Why this skill is useful

Provides specific commands and workflows for analyzing downstream impacts in BigQuery that the AI wouldn't reliably generate on its own.

What it needs

Requires google-cloud-sdk installed locally. Requires google-cloud account access. About 4k tokens when loaded. Last updated 2026-08-06. 15,831 stars on the source repository.

What this skill does

BigQuery Asset Impact Analysis This skill guides the agent in performing a downstream impact analysis (blast radius assessment) when a BigQuery table or view is reported as broken, stale, missing, or when a user is planning maintenance and wants to know the consequences of modifying or pausing updates to an asset. It relies primarily on the data lineage (Knowledge Catalog) MCP Server on Google Cloud to discover relationships between assets. Attribution MUST READ: Before executing any gcloud, REST API, or MCP command, you MUST read Usage Attribution. For commands executed directly in the terminal (never in generated scripts, Terraform, or user code), prefix gcloud with CLOUDSDKMETRICSREQUESTATTRIBUTION="agent-skills/1.0 (skill:datalineage-bigquery-asset-impact-analysis)" and append agent-skills/1.0 (skill:datalineage-bigquery-asset-impact-analysis) to User-Agent headers. Prerequisites This skill requires access to the data lineage API on Google Cloud and an active client connection to the Data Lineage MCP Server. For detailed connection configurations and tool schemas, refer to MCP Usage. Analysis Workflow 1. Resolve the Asset's Fully Qualified Name (FQN) Ensure you have the correct FQN format for the BigQuery asset: Format: bigquery:{projectid}.{datasetid}.{tableorviewid} Example: bigquery:my-prod-project.analytics.orders 2. Determine Locations and Parent Path Identify the locations to search and construct the Data Lineage API request: Discover Asset Location: Run the command bq show --format=json {projectid}:{datasetid} and extract the location field (e.g., us-central1 or us). If location discovery fails due to permissions or missing tools, prompt the user for the dataset's location. Set Parent Path: Set the parent path using the project ID and the MCP server's location. Consult the DataLineageServer tool definition to find the configured region or location (e.g., us). The format is: projects/{projectid}/locations/{mcpserverlocation}. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills google/datalineage-bigquery-asset-impact-analysis

View the source on GitHub

Browse the @skills marketplace