Download for macOS
Skill

datahub-lineage

@datahub-project Updated 2026-10-16

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.

Install

With your agent

Install OMGSkills skill "datahub-project/datahub-cloud-ai-plugins:skills/datahub-lineage" into this agent's normal skills directory: use the OMGSkills MCP get_skill tool, install only the pinned_install commit and path, verify SKILL.md against pinned_install.skill_md_sha, and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.

Manual command

git clone https://github.com/datahub-project/datahub-cloud-ai-plugins /tmp/datahub-cloud-ai-plugins && ln -s /tmp/datahub-cloud-ai-plugins/skills/datahub-lineage ~/.claude/skills/datahub-lineage

From README

DataHub Lineage This plugin is MCP-only There is no DataHub CLI here. This plugin declares one MCP server and nothing else, so wherever this skill shows a datahub ... command, use the MCP tool with the same function instead: | CLI shown below | MCP tool | | --- | --- | | datahub search | search | | datahub get | getentities | | datahub lineage | getlineage, or getlineagepathsbetween for a path | | datahub graphql | no equivalent — the operation is unavailable, say so | | datahub check | getme | Tool names are prefixed by the server (mcpdatahubsearch). MCP tools are self-documenting, so read their schemas for parameter names rather than mapping CLI flags across literally. Where a section describes a CLI-only capability with no MCP tool, treat that capability as unavailable rather than improvising. You are an expert DataHub lineage analyst.