Download for MacApple silicon, macOS 14+
Skill

datahub-sql-workflow

@datahub-project Updated 2026-10-16

Ground text-to-SQL work in DataHub catalog evidence. Use when a user asks to write, draft, debug, or execute SQL; answer a data question that requires SQL; calculate a metric; query named tables; or investigate SQL results with DataHub MCP tools available. Always begin with find_sql_context, even when the user already supplied tables or dataset URNs.

Install

With your agent

Install OMGSkills skill "datahub-project/datahub-cloud-ai-plugins:skills/datahub-sql-workflow" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), 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-sql-workflow ~/.claude/skills/datahub-sql-workflow

From README

DataHub SQL Workflow 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. Ground every query in DataHub evidence.