How do I install the Using Datahub skill?

Run npx skillmds@latest add datahub-project-datahub-skills/using-datahub in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Using Datahub safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Using Datahub?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Using Datahub free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Using Datahub?

datahub-project (@datahub-project-datahub-skills) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Using Datahub by datahub-project-datahub-skills

Name: Using Datahub
Rating: 4.5 (4 reviews)
Author: datahub-project

Using Datahub

This skill provides routing guidance for all DataHub interaction skills. It is injected at session start and helps map user intent to the correct skill. Do not invoke this skill directly — it is loaded automatically.

File contents

Using DataHub Skills

You have access to 5 DataHub catalog interaction skills. Use this guide to route the user's request to the correct skill.

Skill Routing Table

User Intent	Skill	Command
Find or discover entities (search, browse, filter, list)	Search	`/datahub-search`
Answer a question about the catalog ("who owns X?", "how many X?")	Search	`/datahub-search`
Update metadata (descriptions, tags, glossary terms, ownership, deprecation)	Enrich	`/datahub-enrich`
Explore lineage (upstream, downstream, impact, root cause, dependencies)	Lineage	`/datahub-lineage`
Data quality (assertions, incidents, health checks)	Quality	`/datahub-quality`
Notifications (subscribe to assertion failures, incidents)	Quality	`/datahub-quality`
Install CLI, authenticate, verify connection	Setup	`/datahub-setup`
Configure default scopes and profiles	Setup	`/datahub-setup`

Disambiguation Rules

When the intent is ambiguous, use these rules:

"Tag" requests

All tag operations (PII, sensitive, important, reviewed, team-x) → Enrich (general metadata)

"Domain" requests

Filter search to a domain → Search (scoped search)
Configure default domain → Setup (profile configuration)

"Quality" or "health" requests

Failing assertions, active incidents, health status → Quality
Create assertions, run quality checks, raise incidents → Quality
Subscribe to assertion failures or incidents → Quality
Metadata quality/documentation/ownership coverage → Use Search to gather the data and synthesize the answer

Lineage vs. Search

"What feeds into X" / "what depends on X" / "impact of changing X" → Lineage
"What dashboards use table X" → Lineage (relationship traversal)
"Who owns X" / "what is X" → Search (metadata lookup)

Setup vs. other skills

"Set up" / "install" / "authenticate" / "verify connection" → Setup
"Configure defaults" / "set default platform" / "create profile" → Setup
"Check if DataHub is working" → Setup (connectivity verification)

CLI Attribution

When running datahub CLI commands, pass -C skill=<name> on the root command so usage can be attributed:

datahub -C skill=datahub-search search "revenue"
datahub -C skill=datahub-enrich graphql --query '...'
datahub -C skill=datahub-lineage lineage --urn "..."

Use the skill name from the YAML frontmatter. If -C is not recognized, omit it — the command works the same without it.

Critical Rules

Never guess the skill. If the intent is genuinely ambiguous, ask the user to clarify.
One skill per request unless the user explicitly asks for multiple operations.
Lineage is for lineage only — not for general "what is this entity?" questions (that's Search).
Search handles ad-hoc questions. "Who owns X?" and "what columns does X have?" are Search questions, not Lineage.
Enrich handles all metadata writes — descriptions, tags, glossary terms, ownership, deprecation.
Quality handles data quality — assertions, incidents, health checks, subscriptions.
Setup handles environment and configuration — CLI install, auth, connectivity, default scopes.

---name: using-datahubdescription: This skill provides routing guidance for all DataHub interaction skills. It is injected at session start and helps map user intent to the correct skill. Do not invoke this skill directly — it is loaded automatically.---# Using DataHub SkillsYou have access to 5 DataHub catalog interaction skills. Use this guide to route the user's request to the correct skill.---## Skill Routing Table| User Intent | Skill | Command || -------------------------------------------------------------------------------- | ----------- | ------------------ || **Find or discover entities** (search, browse, filter, list) | **Search** | `/datahub-search` || **Answer a question** about the catalog ("who owns X?", "how many X?") | **Search** | `/datahub-search` || **Update metadata** (descriptions, tags, glossary terms, ownership, deprecation) | **Enrich** | `/datahub-enrich` || **Explore lineage** (upstream, downstream, impact, root cause, dependencies) | **Lineage** | `/datahub-lineage` || **Data quality** (assertions, incidents, health checks) | **Quality** | `/datahub-quality` || **Notifications** (subscribe to assertion failures, incidents) | **Quality** | `/datahub-quality` || **Install CLI, authenticate, verify connection** | **Setup** | `/datahub-setup` || **Configure default scopes and profiles** | **Setup** | `/datahub-setup` |---## Disambiguation RulesWhen the intent is ambiguous, use these rules:### "Tag" requests- **All tag operations** (PII, sensitive, important, reviewed, team-x) → **Enrich** (general metadata)### "Domain" requests- **Filter search to a domain** → **Search** (scoped search)- **Configure default domain** → **Setup** (profile configuration)### "Quality" or "health" requests- **Failing assertions, active incidents, health status** → **Quality**- **Create assertions, run quality checks, raise incidents** → **Quality**- **Subscribe to assertion failures or incidents** → **Quality**- **Metadata quality/documentation/ownership coverage** → Use **Search** to gather the data and synthesize the answer### Lineage vs. Search- **"What feeds into X" / "what depends on X" / "impact of changing X"** → **Lineage**- **"What dashboards use table X"** → **Lineage** (relationship traversal)- **"Who owns X" / "what is X"** → **Search** (metadata lookup)### Setup vs. other skills- **"Set up" / "install" / "authenticate" / "verify connection"** → **Setup**- **"Configure defaults" / "set default platform" / "create profile"** → **Setup**- **"Check if DataHub is working"** → **Setup** (connectivity verification)---## CLI AttributionWhen running `datahub` CLI commands, pass `-C skill=<name>` on the root command so usage can be attributed:```bashdatahub -C skill=datahub-search search "revenue"datahub -C skill=datahub-enrich graphql --query '...'datahub -C skill=datahub-lineage lineage --urn "..."```Use the skill name from the YAML frontmatter. If `-C` is not recognized, omit it — the command works the same without it.---## Critical Rules1. **Never guess the skill.** If the intent is genuinely ambiguous, ask the user to clarify.2. **One skill per request** unless the user explicitly asks for multiple operations.3. **Lineage is for lineage only** — not for general "what is this entity?" questions (that's Search).4. **Search handles ad-hoc questions.** "Who owns X?" and "what columns does X have?" are Search questions, not Lineage.5. **Enrich handles all metadata writes** — descriptions, tags, glossary terms, ownership, deprecation.6. **Quality handles data quality** — assertions, incidents, health checks, subscriptions.7. **Setup handles environment and configuration** — CLI install, auth, connectivity, default scopes.

Frequently asked questions