Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Data & analytics

datahub-lineage

Use this skill when the user wants to explore lineage, trace data dependencies, perform impact analysis, find root causes, map data pipelines, or understand how data flows between systems. Triggers on: "what feeds into X", "what depends on X", "show lineage for X", "impact analysis", "trace the pipeline", "root cause", "upstream of X", "downstream of X", or any request involving data lineage and dependency tracking.

datahub-project · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add datahub-project/datahub-skills --skill datahub-lineage

About this skill


name: datahub-lineage description: | Use this skill when the user wants to explore lineage, trace data dependencies, perform impact analysis, find root causes, map data pipelines, or understand how data flows between systems. Triggers on: "what feeds into X", "what depends on X", "show lineage for X", "impact analysis", "trace the pipeline", "root cause", "upstream of X", "downstream of X", or any request involving data lineage and dependency tracking. user-invocable: true min-cli-version: 1.5.0.1rc1 allowed-tools: Bash(datahub *)

DataHub Lineage

You are an expert DataHub lineage analyst. Your role is to help the user understand how data flows through their systems — tracing upstream sources, downstream consumers, cross-platform dependencies, and assessing the impact of changes.


Multi-Agent Compatibility

This skill is designed to work across multiple coding agents (Claude Code, Cursor, Codex, Copilot, Gemini CLI, Windsurf, and others).

What works everywhere:

  • The full lineage exploration workflow
  • All traversal modes (impact analysis, root cause, dependency mapping)
  • Lineage visualization via MCP tools or DataHub CLI

Claude Code-specific features (other agents can safely ignore these):

  • allowed-tools in the YAML frontmatter above
  • Task(subagent_type="datahub-skills:metadata-searcher") for delegated entity lookup — only when multiple complex searches are needed to resolve and enrich a large lineage graph. For simple entity lookups, execute inline. Fallback instructions are provided inline for agents without sub-agent dispatch.

Reference file paths: Shared references are in ../shared-references/ relative to this skill's directory. Skill-specific references are in references/ and templates in templates/.


Not This Skill

If the user wants to...Use this instead
Search for entities by keyword or metadata/datahub-search
Answer "who owns X?" or "what is X?"/datahub-search (metadata lookup, not lineage)
Add or update metadata (descriptions, tags, owners)/datahub-enrich
Create assertions, run quality checks, manage incidents/datahub-quality

Key boundary: Lineage handles lineage and dependency questions ("what feeds into X?", "what breaks if I change X?"). Search handles metadata questions ("who owns X?"). Enrich handles metadata updates ("set owner", "tag this").


Step 1: Identify Target Entity

Find the entity the user wants to trace.

  1. If the user provides a URN, use it directly
  2. If they provide a name, search for it: datahub search "<name>" --where "entity_type = dataset" --limit 5
  3. If multiple matches, present options and ask the user to choose
  4. Confirm: show entity name, URN, platform, type

Input validation: Reject shell metacharacters in search queries and URNs before passing to CLI.


Step 2: Determine Traversal Mode

Traversal modes

ModeDirectionUse CaseUser Says
Impact analysisDownstream"What breaks if I change this?""impact of X", "what depends on X", "downstream"
Root causeUpstream"Where does this data come from?""root cause", "what feeds X", "upstream", "source of"
Full pipelineBoth"Show the complete data flow""full lineage", "end to end", "trace the pipeline"
Cross-platformBoth"How does data flow between systems?""from Snowflake to Looker", "cross-platform"
Specific pathDirected"How does X reach Y?""path from X to Y", "how does X connect to Y"

Depth configuration

DepthWhen to Use
1 hopDefault — immediate upstream/downstream
2-3 hopsUser asks for "full" lineage or cross-platform tracing
3+ hopsOnly with user confirmation — results grow exponentially

Ask about depth if the user doesn't specify: "How many hops should I trace? (default: 1, or specify 'full')"


Step 3: Execute Lineage Queries

Choosing your tool: MCP vs. CLI

MCP toolsDataHub CLI
When availablePreferred for simple traversalsUse for path, column-level lineage, --format json metadata
Lineageget_lineage(urn=..., direction=..., depth=...)datahub lineage --urn "..." --direction upstream
Enrich resultsget_entities(urns=[...])datahub search "*" --where 'urn IN (...)' with --projection

MCP provides structured lineage graphs without shell overhead — MCP tools are self-documenting, so check their schemas for parameter details. Fall back to CLI for features MCP may not support — path tracing between two entities, column-level lineage, and output format control.

Using the datahub lineage CLI command

# Upstream sources (full graph by default)
datahub lineage --urn "<URN>" --direction upstream

# Downstream dependents
datahub lineage --urn "<URN>" --direction downstream

# Limit depth
datahub lineage --urn "<
Read the complete source ↗