datalineage-bigquery-asset-impact-analysis

Analyzes downstream blast radius of broken or modified BigQuery tables and views using Data Lineage API.

Updated May 11, 2026
One-click install
npx skills add https://github.com/alon3153/upe-social-publisher --skill datalineage-bigquery-asset-impact-analysis-alon3153
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: datalineage-bigquery-asset-impact-analysis
Source: https://github.com/alon3153/upe-social-publisher/tree/main/.agents/skills/datalineage-bigquery-asset-impact-analysis
Command: npx skills add https://github.com/alon3153/upe-social-publisher --skill datalineage-bigquery-asset-impact-analysis-alon3153

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When a BigQuery table or view breaks, goes stale, or needs modification, teams struggle to know which downstream tables, dashboards, and pipelines will be affected. This Skill performs a structured blast radius analysis so you can assess consequences before making changes. ## Core Features & Use Cases - Downstream Lineage Discovery: Uses the Google Cloud Data Lineage MCP server's search_lineage tool to retrieve all downstream dependencies up to a configurable depth. - Impact Classification: Distinguishes direct impacts (depth 1, including exact copies) from indirect cascading impacts, and identifies the transform processes (ETL pipelines, views, scheduled queries) propagating the data. - Structured Reporting: Produces an executive summary, critical path highlights, a complete blast radius table, and analysis metadata showing search boundaries. - Use Case: Before pausing updates to bigquery:my-prod-project.analytics.orders, run this analysis to discover that three reporting views and a production dashboard depend on it, so you can notify owners in advance. ## Quick Start Analyze the downstream impact if the BigQuery table my-project.analytics.orders becomes stale or is modified.

Frequently Asked Questions about datalineage-bigquery-asset-impact-analysis

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

FAQPage Schema
How do I find downstream dependencies of a BigQuery table?▼

Use the Data Lineage MCP server's search_lineage tool with direction set to DOWNSTREAM and the table's fully qualified name in bigquery:project.dataset.table format. It returns lineage links showing dependent assets and the processes connecting them.

How to assess impact before modifying a BigQuery table?▼

Run a downstream lineage search with max_depth around 10, then classify results into direct impacts at depth 1 and indirect cascading impacts at greater depths. Highlight assets with names containing prod, dashboard, or reporting as critical paths.

Does BigQuery lineage analysis work for views and scheduled queries?▼

Yes, the lineage graph includes views and scheduled queries as transform processes in the processes field of each link. Both tables and views can be analyzed as source assets using the same fully qualified name format.

Why does BigQuery lineage search return empty results?▼

An empty response means no downstream dependencies exist in the queried locations. Verify the dataset location with bq show and confirm the search locations array includes it, then consider expanding the locations or depth limits.

Can I use gcloud CLI instead of the Data Lineage MCP tool?▼

No, gcloud does not support lineage link searches in standard or beta tracks. The tool preference hierarchy is the Data Lineage MCP search_lineage tool first, then bq CLI, with gcloud unsuitable for lineage queries.