Generated banner for Datalineage Bigquery Asset Impact Analysis
Generated logo for Datalineage Bigquery Asset Impact Analysis

Datalineage Bigquery Asset Impact Analysis

GoogleOfficialPublished by Google

  • Skill
  • Research and analysis
  • Data and AI
  • Apache-2.0
  • No issues found

From the author

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.
— the description by Google

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill enables agents to perform a comprehensive blast radius analysis for Google Cloud BigQuery assets. By leveraging the Data Lineage MCP server, the agent identifies downstream dependencies, including tables, views, and ETL processes, that may be affected by modifications, deletions, or service interruptions. It provides a structured workflow to resolve asset names, query lineage relationships, and present a clear impact report to the user.

What it does

  • Resolves BigQuery assets to their fully qualified names.
  • Queries downstream lineage using the Data Lineage MCP server.
  • Maps dependencies across tables, views, and transformation processes.
  • Categorizes impact as direct or indirect based on lineage depth.
  • Generates a summary report including a detailed blast radius table.
  • Provides metadata on search parameters for transparency and refinement.

When to use it

  • When planning maintenance or modifications to a BigQuery table or view.
  • When assessing the consequences of deleting or pausing updates to a data asset.
  • When investigating the potential impact of a broken or stale data asset.
  • When identifying all downstream dashboards and processes dependent on a specific table.

Advantages

  • Reduces risk by identifying hidden dependencies before making changes.
  • Provides clear visibility into cascading failures across data pipelines.
  • Uses standardized lineage tools for accurate dependency mapping.
  • Ensures consistent reporting through a structured output format.

Usage examples

“What is the blast radius if I delete the table bigquery:my-project.analytics.sales_data?”
The agent will search for all downstream dependencies of the specified table and present a table showing affected assets, the processes involved, and the depth of the impact.
“I need to pause updates to the 'daily_metrics' view. Which dashboards will be affected?”
The agent will perform a downstream lineage search and highlight any downstream assets identified as dashboards or reporting tables.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/google/datalineage-bigquery-asset-impact-analysis/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip datalineage-bigquery-asset-impact-analysis.zip -d .agents/skills

Documentation by Google

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 CLOUDSDK_METRICS_REQUEST_ATTRIBUTION="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:{project_id}.{dataset_id}.{table_or_view_id}

    • 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 {project_id}:{dataset_id} 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/{project_id}/locations/{mcp_server_location}.

  • Configure Search Scope: Include the discovered asset location in the locations array of the payload (e.g., ["us-central1"] or ["us", "us-central1"]).

3. Retrieve the Downstream Lineage Graph

Call the DataLineageServer:search_lineage tool to fetch downstream relationships.

  • Direction: Set to DOWNSTREAM.

  • Search Parameters: Use max_depth = 10 and max_process_per_link = 5 as robust defaults.

4. Identify the Blast Radius

Traverse the returned lineage links to build the impact graph:

  • Affected Assets: The target of each link represents a downstream asset that depends on your source asset.

  • Transform Processes: Inspect the processes field on each link. This identifies the ETL pipelines, BigQuery Views, or Scheduled Queries that propagate the data.

  • Direct vs. Indirect Impact:

    • Direct Impact (Depth 1): Assets directly consuming the source asset. If a link has dependency_type: EXACT_COPY, mark the target as "Directly Stale / Identical Copy".

    • Indirect Impact (Depth > 1): Assets further down the stream that will experience cascading stale data or failures.

5. Summarize and Format the Output

Present your findings clearly to the user using the following structure:

  1. Executive Summary: State the total number of downstream assets affected and the maximum depth of the impact.

  2. Critical Path: Highlight high-priority downstream assets (e.g., assets containing "prod", "dashboard", "reporting", or "master" in their names).

  3. Blast Radius Table: A clean Markdown table listing the dependencies. You MUST include all columns:

    Downstream AssetTransform ProcessDepthImpact Type
    bigquery:project.dataset.tableprojects/p/locations/l/processes/proc1Direct
    bigquery:project.dataset.viewprojects/p/locations/l/processes/view2Indirect
  4. Analysis Metadata: Provide transparency on the parameters and boundaries of your search so the user can choose to expand them:

    • Locations Searched: {list_of_locations_queried}

    • Parent Location: {parent_path}

    • Depth Limit: {max_depth}

    • Process per Link Limit: {max_process_per_link}

    • Tip for User: Let the user know they can request to rerun the analysis with expanded locations or larger depth limits.

Crucial Constraints & Guardrails

  1. Interpret Empty Responses Correctly:

    • If the lineage response is empty, immediately assume that no dependencies exist in the queried locations and report this to the user.

  2. Strictly Banned Bypasses:

    • Exclusively retrieve downstream relationships using the DataLineageServer:search_lineage tool.

  3. Verify Asset Existence First:

    • If bq show indicates the source table does not exist, stop and report this directly to the user. Do not attempt to guess alternative table names unless the user explicitly instructs you to do so.

  4. No Output Shortcutting or Hallucinated Artifacts:

    • Present the complete downstream blast radius table directly in your final response. Avoid telling the user you have created a separate Markdown file or artifact containing the details unless you have explicitly executed file-writing tools to create it.

Reference Directory

  • MCP Usage: Using the data lineage remote MCP server on Google Cloud and tool preferences.

External Documentation

Files

LICENSE


                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs an MCP server

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Google
Publisher
Google (Official)
Source
google/skills · skills/cloud/datalineage-bigquery-asset-impact-analysis · commit 2194d3b
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Google.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download datalineage-bigquery-asset-impact-analysis.zip