Official agent skill

Datalineage Bigquery Asset Impact Analysis

by google in google/skills

Analyzes the downstream impact (blast radius) using data lineage on Google Cloud when a BigQuery table or view is broken, stale, or modified.

OfficialApache-2.0Auto-check passedDatabases

Install Datalineage Bigquery Asset Impact Analysis

skills CLI
$ npx skills add google/skills --skill datalineage-bigquery-asset-impact-analysis -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install google/skills datalineage-bigquery-asset-impact-analysis --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/google/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/cloud/datalineage-bigquery-asset-impact-analysis .claude/skills/datalineage-bigquery-asset-impact-analysis && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
datalineage-bigquery-asset-impact-analysis
GitHub stars
21k
Token cost
~1.7k tokens
SKILL.md length
670 words
Files
2 (incl. references)
Skills in repo
150
Repo updated
First seen
Licence
Apache-2.0

At a glance

Analyzes the downstream impact (blast radius) using data lineage on Google Cloud when a BigQuery table or view is broken, stale, or modified.

  • Works in 5 steps: Resolve the Asset's Fully Qualified Name… → Determine Locations and Parent Path → Retrieve the Downstream Lineage Graph → …
  • : - Performing a blast radius
  • SKILL.md covers Prerequisites, Analysis Workflow, Crucial Constraints & Guardrails and Reference Directory, plus 1 more section
  • Calls bq

What it does

Datalineage Bigquery Asset Impact Analysis is an agent skill from google/skills, published by the product's own GitHub organization. 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: -…

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/mcp-usage.md`).

It sits in Databases, covering Data warehousing and Data governance. It works with Google BigQuery, Google Cloud and Model Context Protocol. The repository describes itself as: Agent Skills for Google products and technologies. The licence is Apache-2.0.

When your agent uses it

  • : - Performing a blast radius
  • Impact analysis for a BigQuery table
  • : - General BigQuery querying
  • Data analysis (use BigQuery-related tools instead)

Example prompts

  • “Use the datalineage-bigquery-asset-impact-analysis skill to analyz the downstream impact (blast radius) using data lineage on Google Cloud when a…”
  • “/datalineage-bigquery-asset-impact-analysis”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Resolve the Asset's Fully Qualified Name (FQN)
  2. Determine Locations and Parent Path
  3. Retrieve the Downstream Lineage Graph
  4. Identify the Blast Radius
  5. Summarize and Format the Output

What it can do on your machine

Read from SKILL.md and the folder at commit 4b940dd. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • bq

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • cloud.google.com
    • docs.cloud.google.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Datalineage Bigquery Asset Impact Analysis loads about 1.7k tokens when it runs, and up to ~2k if it reads all its reference files. Until then it costs about 195 tokens; SKILL.md has 670 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~195
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from google/skills at commit 4b940dd, republished under its Apache-2.0 licence (© google). 670 words, ~1,673 tokens.

Download SKILL.mdSave it as .claude/skills/datalineage-bigquery-asset-impact-analysis/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
datalineage-bigquery-asset-impact-analysis
description
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.
metadata.version
1.0.1
metadata.category
BigDataAndAnalytics

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.

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.
Show full SKILL.md (303 more words)Show less
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

© google, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/cloud/datalineage-bigquery-asset-impact-analysis of google/skills.

  • SKILL.md
  • references/mcp-usage.md

Open the folder on GitHubat commit 4b940dd

Compare with similar skills

Datalineage Bigquery Asset Impact Analysis next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Datalineage Bigquery Asset Impact Analysis compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Datalineage Bigquery Asset Impact Analysis this skillgoogle/skills21k—~1.7kAutomated safety check: PassApache-2.0
Imaging Data CommonsK-Dense-AI/scientific-agent-skills48k1 repos~7.8kAutomated safety check: PassMIT
Semantic Analystsidequery/sidemantic129—~982Automated safety check: PassAGPL-3.0
GCP Audit Logssickn33/agentic-awesome-skills47k2 repos~3.8kAutomated safety check: PassMIT
Bigquery Basicsdavila7/claude-code-templates33k—~1.1kAutomated safety check: PassMIT
Deploying On GCPancoleman/ai-design-components525—~3.9kAutomated safety check: PassMIT

Similar skills

  • Imaging Data Commons

    K-Dense-AI/scientific-agent-skills

    Queries and downloads public cancer imaging data from NCI Imaging Data Commons.

    48k GitHub starsUsed in 1 repo~7.8k tokens
    DatabasesAuto-check passed
  • Semantic Analyst

    sidequery/sidemantic

    Answer analytical, KPI, metric, trend, cohort, and business-performance questions through a Sidemantic semantic layer.

    129 GitHub stars~982 tokensUpdated 3 days ago
    DatabasesAuto-check passed
  • GCP Audit Logs

    sickn33/agentic-awesome-skills

    Configure GCP Cloud Audit Logs for compliance. An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~3.8k tokens
    DatabasesAuto-check passed
  • Bigquery Basics

    davila7/claude-code-templates

    Manages datasets, tables, and jobs in BigQuery, and integrates with BigQuery ML and Gemini for advanced data analytics and AI-driven insights.

    33k GitHub stars~1.1k tokensUpdated today
    DatabasesAuto-check passed
  • Deploying On GCP

    ancoleman/ai-design-components

    Implement applications using Google Cloud Platform (GCP) services.

    525 GitHub stars~3.9k tokensUpdated 10 mo ago
    DatabasesAuto-check passed
  • Querying Data Lake

    aws/agent-toolkit-for-aws

    Official

    Execute and manage Athena SQL queries across default and federated catalogs (Glue, S3 Tables, Redshift).

    2.8k GitHub stars~1.9k tokensUpdated today
    DatabasesAuto-check passed

More from google/skills

All 150 skills in this repo
  • Official

    Query Cloud Trace spans, filter by latency thresholds or error status, correlate distributed traces with Cloud Logging, and diagnose latency bottlenecks across Google Cloud services.

    21k GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Official

    Manages Google Cloud Privileged Access Manager entitlements and grants: create and edit entitlements, request temporary access, and approve or deny pending grants.

    21k GitHub stars~3.2k tokensUpdated today
    Auto-check passed
  • Official

    Writes Terraform alerting policies for AI agents that emit OpenTelemetry metrics, covering reliability, cost, safety, security and quality signals on Google Cloud.

    21k GitHub stars~4.2k tokensUpdated today
    Auto-check passed
  • Official

    Deploys open models or custom weights from Model Garden to Agent Platform endpoints, checks deployment status and cleans up endpoints, confirming before any change.

    21k GitHub stars~5k tokensUpdated today
    Auto-check passed
  • Official

    Searches, manages and scaffolds skills in the Gemini Enterprise Agent Platform Skill Registry using bundled Python scripts and Google Cloud credentials.

    21k GitHub stars~584 tokensUpdated today
    Auto-check passed
  • Designs GCP infrastructure as local Terraform, validates and scans it against best practices, then imports it to Application Design Center for deployment and troubleshooting.

    21k GitHub stars~4.4k tokensUpdated today
    Auto-check passed

Categories

Questions about Datalineage Bigquery Asset Impact Analysis

What does Datalineage Bigquery Asset Impact Analysis do?

Analyzes the downstream impact (blast radius) using data lineage on Google Cloud when a BigQuery table or view is broken, stale, or modified. Datalineage Bigquery Asset Impact Analysis is an agent skill from google/skills, published by the product's own GitHub organization. Analyzes the downstream impact (blast radius) using data lineage on Google Cloud when a BigQuery table or view is broken, stale, or modified.

When should I use Datalineage Bigquery Asset Impact Analysis?

Datalineage Bigquery Asset Impact Analysis fits situations like: : - Performing a blast radius; impact analysis for a BigQuery table; : - General BigQuery querying; data analysis (use BigQuery-related tools instead).

How do I install Datalineage Bigquery Asset Impact Analysis in Claude Code?

Run `npx skills add google/skills --skill datalineage-bigquery-asset-impact-analysis -a claude-code`. Or copy the skill folder (skills/cloud/datalineage-bigquery-asset-impact-analysis in google/skills) into .claude/skills/datalineage-bigquery-asset-impact-analysis in your project. Claude Code loads it when a task matches its description.

How do I install Datalineage Bigquery Asset Impact Analysis in Codex?

Run `npx skills add google/skills --skill datalineage-bigquery-asset-impact-analysis -a codex`. Or copy the skill folder (skills/cloud/datalineage-bigquery-asset-impact-analysis in google/skills) into .agents/skills/datalineage-bigquery-asset-impact-analysis in your project. Codex loads it when a task matches its description.

Can I use Datalineage Bigquery Asset Impact Analysis in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add google/skills --skill datalineage-bigquery-asset-impact-analysis -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/datalineage-bigquery-asset-impact-analysis, .gemini/skills/datalineage-bigquery-asset-impact-analysis, .github/skills/datalineage-bigquery-asset-impact-analysis and .opencode/skills/datalineage-bigquery-asset-impact-analysis in your project.

What does Datalineage Bigquery Asset Impact Analysis need to run?

Going by SKILL.md and its folder, Datalineage Bigquery Asset Impact Analysis needs the command-line tools its instructions call (bq).

Does Datalineage Bigquery Asset Impact Analysis access the network?

SKILL.md names 2 domains. As links in the text: cloud.google.com and docs.cloud.google.com. This is read from the text; nothing was executed.

Is Datalineage Bigquery Asset Impact Analysis safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Datalineage Bigquery Asset Impact Analysis use?

Datalineage Bigquery Asset Impact Analysis is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Datalineage Bigquery Asset Impact Analysis use?

About 1.7k tokens (SKILL.md is roughly 6.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 311 tokens, read only when the agent opens those files.

What are the alternatives to Datalineage Bigquery Asset Impact Analysis?

Skills that share tags, products or a category with Datalineage Bigquery Asset Impact Analysis: Imaging Data Commons (K-Dense-AI/scientific-agent-skills, 48k stars), Semantic Analyst (sidequery/sidemantic, 129 stars), GCP Audit Logs (sickn33/agentic-awesome-skills, 47k stars) and Bigquery Basics (davila7/claude-code-templates, 33k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Datalineage Bigquery Asset Impact Analysis?

google (a GitHub organization, an official publisher) maintains it in google/skills, which has 21,097 GitHub stars. The repository holds 150 skills in this directory. The repository was last updated on October 9, 2026.

Source: google/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.