lineage

Data Lineage Guide

Overview

Use this skill any time the user wants to understand data flow, trace data origins, identify downstream impacts, or analyze how data pipelines have changed over time. This skill guides users through exploring data lineage relationships in a structured way, ensuring they understand the scope and depth of lineage traversal before executing queries.

Phase 0: Intent Detection and Entry Path Selection

Always start by understanding what the user wants to accomplish and which entry path is most appropriate:

Entry Path A: Direct Lineage Search (Lineage-First)

Use when the user mentions an asset name but doesn't specify a catalog/project context, or when they want to search across all lineage assets.

• Tool: search_lineage_assets
• Best for: "Find the lineage for CUSTOMER_360", "What feeds into the sales table?"
• Supports: Optional filters for technology type and asset type

Entry Path B: Catalog Asset Lookup (Catalog-First)

Use when the user references a known catalog or project asset, or provides specific container context.

• Tools: search_asset → convert_asset_to_lineage_id
• Best for: "Show lineage for the ORDERS table in the sales catalog", "Trace the customer_data asset in AgentTest project"
• Requires: Container context (catalog or project name)

Decision Logic:

• If user mentions "catalog" or "project" name → Use Path B (Catalog-First)
• If user only provides asset name without container → Use Path A (Lineage-First)
• If uncertain → Ask user to clarify or default to Path A

Phase 1: Asset Identification

Locate the starting asset(s) in the lineage graph using the appropriate entry path.

Path A: Direct Lineage Search