Agent skill · data analytics · google

datalineage-summary

Summarizes data lineage graphs on Google Cloud to help users debug data quality issues and understand data provenance for BigQuery and Cloud Storage. Use when summarizing upstream and downstream data flows, and presenting complex lineage data as an intuitive Markdown report. Don't use for generic BigQuery queries, editing lineage relationships, or downstream deprecation. Don't use for downstream blast-radius impact analysis (use datalineage-bigquery-asset-impact-analysis skill instead).

Why this skill is useful

Provides specific commands and configurations for querying Google Cloud Data Lineage that the AI wouldn't reliably generate on its own.

What it needs

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

What this skill does

Data Lineage Summary This skill guides the agent in investigating and summarizing the Data Lineage graph for a specific focal asset (Table-Level Lineage) or specific fields (Column-Level Lineage). It provides an intuitive left-to-right walkthrough of how data enters and leaves the asset, abstracting away complex node and link details into plain English. 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-summary)" and append agent-skills/1.0 (skill:datalineage-summary) to User-Agent headers. Prerequisites This skill relies on the data lineage (Knowledge Catalog) MCP Server on Google Cloud for graph traversal. Ensure you can run searchlineage queries in both upstream and downstream directions. For detailed connection configurations and tool schemas, refer to MCP Usage. Workflow Logic 1. Get Lineage Fetch the lineage graph in both directions from the focal point (both upstream and downstream) by making two separate calls to the MCP tool: one with "direction": "UPSTREAM" and another with "direction": "DOWNSTREAM". Location Strategy: You MUST use the readurl tool to fetch the comprehensive list of locations dynamically from the provided Knowledge Catalog Locations link. To ensure cross-regional lineage is not missed, always verify the current list of Google Cloud regions using this link before populating the locations array. You MUST populate the locations array with all supported physical regions fetched from this link. You may optionally additionally determine the asset's specific active region (using bq show or gcloud storage ls). Search Parameters: Use maxDepth = 10, maxResults = 5000 and maxProcessPerLink = 10 as robust defaults when calling searchlineage. …

How to use it

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

@skills google/datalineage-summary

View the source on GitHub

Browse the @skills marketplace