What problem does it solve?
Understanding how data flows into and out of a BigQuery table or GCS asset requires navigating complex lineage graphs of nodes and links, which is difficult to interpret when debugging data quality issues or verifying data provenance.
Core Features & Use Cases
- Bidirectional Lineage Retrieval: Queries the Google Cloud Data Lineage MCP server in both upstream and downstream directions with configurable depth, location, and result limits.
- Table and Column-Level Lineage: Supports Table-Level Lineage and Column-Level Lineage via wildcard or specific field configuration in search_lineage calls.
- Plain-English Markdown Summaries: Produces a left-to-right narrative covering overall flow type, systems involved, upstream sources, downstream consumers, and analysis metadata.
- Use Case: A data engineer investigating a corrupted BigQuery reporting table uses this Skill to trace which upstream Dataproc jobs and source tables feed it, and which downstream dashboards consume it, receiving a readable summary instead of raw graph data.
Quick Start
Summarize the upstream and downstream data lineage for the BigQuery table my-project.my_dataset.my_table and explain where its data comes from and goes.