What is datalineage-bigquery-asset-impact-analysis?

A BigQuery impact-analysis skill that traces which tables, dashboards, and processes depend on a table or view.

Use it to assess the blast radius of modifying or stopping updates to a BigQuery table or view.

It shows the downstream consequences of an asset being broken, stale, changed, or paused before maintenance begins.

datalineage-bigquery-asset-impact-analysis — Skill for Claude Code and

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add hamzabellouch/agent-skills --skill datalineage-bigquery-asset-impact-analysis

Clone the repo

git clone --depth 1 https://github.com/hamzabellouch/agent-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/hamzabellouch/agent-skills/datalineage-bigquery-asset-impact-analysis/github.svg)](https://agentmods.dev/skills/hamzabellouch/agent-skills/datalineage-bigquery-asset-impact-analysis)

Your own site

<a href="https://agentmods.dev/skills/hamzabellouch/agent-skills/datalineage-bigquery-asset-impact-analysis"><img src="https://agentmods.dev/badge/skills/hamzabellouch/agent-skills/datalineage-bigquery-asset-impact-analysis/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/hamzabellouch/agent-skills/datalineage-bigquery-asset-impact-analysis"><img src="https://agentmods.dev/badge/skills/hamzabellouch/agent-skills/datalineage-bigquery-asset-impact-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 159 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,521 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00159	$0.01521
Opus 5	$0.00079	$0.00760
Sonnet 5	$0.00032	$0.00304
Haiku 4.5	$0.00016	$0.00152

Measured 9d ago against content hash c68617bcc90e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

datalineage-bigquery-asset-impact-analysis scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to datalineage-bigquery-asset-impact-analysis — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

Google Cloud and GKE/datalineage-bigquery-asset-impact-analysis/SKILL.md · 137 lines

How it starts

The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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 Google Cloud Data Lineage (Knowledge Catalog) MCP Server to discover relationships between assets.

Prerequisites

This skill requires access to the Google Cloud Data Lineage API 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.

Read the full file on GitHub · 137 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

references/mcp-usage.md 1.2 KB

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

9d ago First seen · 137 lines · 159 tokens per session scan A c68617bcc90e

Subscribe to this mod's changes

datalineage-bigquery-asset-impact-analysis is a skill published in the GitHub repository hamzabellouch/agent-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 159 tokens to every session and 1,521 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to datalineage-bigquery-asset-impact-analysis, differing in 0 lines, and is treated as a copy.

Analytics and metrics Claude Code Databases PostgreSQL agent-skills ai-agent antigravity codex-cli cursor

datalineage-bigquery-asset-impact-analysis

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

This is a copy

How it starts

BigQuery Asset Impact Analysis

Prerequisites

Analysis Workflow

1. Resolve the Asset's Fully Qualified Name (FQN)

2. Determine Locations and Parent Path

3. Retrieve the Downstream Lineage Graph

What ships with it

What this file has done since we first saw it

Other skills, from other repositories

db-performance

backup-restore

postgres-operations

cockroachdb

cosmosdb

postgresql