⏳ This skill is pending AI review.

Scores will appear once the review pipeline completes.

version unknown

openmetadata-workflow

@open-metadata⭐ 15.4k stars

Meta-skill loaded at session start. Directs Claude to check for applicable OpenMetadata skills before starting any task. Ensures structured workflows are followed.

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

—/10

// RATINGS

⭐GitHub Stars
⭐⭐⭐⭐⭐ 15.4k on GitHubGitHub ↗

Very popular

🟢ProSkills Score
—
📍

Not yet listed on ClawHub or SkillsMP

// README

OpenMetadata

Commit Activity Release

The Open Context Layer for AI

The largest and fastest-growing open-source project for AI context, data cataloging, and metadata management.

OpenMetadata is the open platform for trusted data context, organizational memory, and business semantics for every data user, AI assistant, and agent.

OpenMetadata connects technical metadata, data quality signals, lineage, column-level lineage, ownership, usage, policies, conversations, memories, glossaries, classifications, metrics, domains, data contracts, and data products into a unified metadata knowledge graph. With 130+ connectors, open metadata standards, semantic search, APIs, SDKs, and an MCP server, OpenMetadata gives every user and AI system the governed context it needs to discover, understand, trust, remember, and use data.

AI does not need another raw database connector. AI needs context + memory.

OpenMetadata: The Open Context Layer for AI

OpenMetadata provides the context AI needs to know:

  • what data exists
  • what it means
  • who owns it
  • how it is used
  • where it came from
  • where it flows
  • whether it is fresh, tested, certified, and trusted
  • which business concepts, classifications, glossary terms, policies, contracts, and data products apply
  • what downstream dashboards, pipelines, metrics, ML models, and applications depend on it
  • what conversations, decisions, assumptions, and memory nuggets have already been captured about it

Why OpenMetadata for AI?

AI systems need more than data access. They need governed context, business meaning, trust signals, lineage, usage, ownership, standards, and organizational memory.

A direct connection to a warehouse, lake, dashboard, or pipeline exposes raw structures. It does not tell an AI assistant what the data means, whether it is certified, who owns it, which policies apply, what contract governs it, what breaks if it changes, or what the organization has already learned about it.

OpenMetadata is the open context layer that gives every data user and AI agent the full picture of enterprise data.

OpenMetadata brings together five capabilities:

  1. Context — technical, operational, trust, usage, and lineage metadata from across the data ecosystem.
  2. Semantics — business meaning through glossaries, metrics, classifications, domains, policies, ontologies, and data products.
  3. Knowledge Graph — relationships connecting assets, columns, people, teams, quality, lineage, policies, memories, contracts, and business concepts.
  4. Memory — conversations, AI threads, decisions, assumptions, runbooks, remediation notes, and reusable memory nuggets that preserve tribal knowledge.
  5. Activation — MCP, Semantic Search, APIs, SDKs, events, and workflows that make context usable by AI assistants, agents, applications, and humans.

With OpenMetadata, users and AI agents can answer:

  • What does this metric mean and how is it calculated?
  • Which datasets power this dashboard?
  • Who owns this data product?
  • Which data contract applies?
  • Is this dataset fresh, tested, certified, and trusted?
  • Which downstream dashboards, pipelines, or ML models are affected by this column change?
  • Which columns contain sensitive customer information?
  • Which glossary terms, policies, standards, and business concepts apply?
  • What decisions, assumptions, incidents, or conversations have already been captured about this asset?

The Context OpenMetadata Connects

OpenMetadata collects and connects the context AI needs to reason safely over enterprise data.

Context typeWhat OpenMetadata capturesWhy it matters for AI
Technical metadataDatabases, schemas, tables, columns, topics, dashboards, charts, pipelines, APIs, search indexes, ML models, storage assets, data types, constraints, descriptions, joins, sample queries, service metadata, owners, teams, usage, domains, and data productsHelps AI discover what exists and understand how assets are structured
Quality and trustTest cases, test suites, freshness checks, volume checks, null, uniqueness, distribution, custom tests, profiling results, observability signals, incidents, alerts, and quality historyHelps AI avoid treating every dataset as equally trustworthy
Lineage and impactUpstream and downstream lineage, table lineage, column-level lineage, dashboard lineage, pipeline lineage, metric lineage, ML model lineage, API and topic dependencies, and OpenLineage eventsHelps AI explain where data came from, where it flows, and what changes may break
SemanticsGlossaries, business terms, synonyms, related terms, metrics, KPIs, classifications, tags, domains, data products, policies, personas, lifecycle states, and ontologiesHelps AI map technical names to business meaning
GovernanceOwners, stewards, teams, policies, roles, classifications, access context, certification, review workflows, lifecycle states, and data contractsHelps AI act with policy-aware context
Memory and tribal knowledgeConversations, AI threads, decisions, assumptions, runbooks, remediation notes, incident learnings, and reusable memory nuggets attached to assets, users, teams, data products, and agent workflowsHelps humans and agents inherit what the organization already learned instead of rediscovering it in every conversation
Standards and interoperabilityDCAT, DPROD, PROV-O, OpenLineage, ODCS, RDF/OWL, JSON-LD, SHACL, JSON Schema, APIs, events, and metadata schemasHelps context move across tools, agents, catalogs, contracts, and knowledge graphs

Architecture: Context + Memory Graph

How OpenMetadata Works

OpenMetadata is built around an open, schema-first metadata graph.

  1. Collect metadata from warehouses, lakes, BI tools, pipelines, ML platforms, messaging systems, storage systems, APIs, search systems, SaaS applications, metadata systems, documents, conversations, and agent workflows through 130+ connectors, ingestion APIs, events, and SDKs.
  2. Normalize metadata with open schemas and standards so every asset, relationship, policy, contract, lineage event, and memory can be represented consistently.
  3. Connect technical metadata, quality signals, lineage, ownership, usage, policies, conversations, memories, semantics, domains, contracts, and data products into one graph.
  4. Preserve Memory by turning conversations, AI threads, decisions, assumptions, runbooks, and remediation notes into reusable governed memory nuggets tied to data assets and business context.
  5. Govern context with open standards, classifications, policies, roles, data quality, review workflows, data contracts, and stewardship.
  6. Activate that context through Semantic Search, MCP, APIs, SDKs, events, webhooks, metadata applications, and AI workflows.

Memory is part of the architecture, not a side channel. It lets engineers use APIs, SDKs, MCP, or AI workflows to preserve conversational context and convert tribal knowledge into reusable organizational knowledge.


Context Graph, Semantics, and Memory

OpenMetadata Context Graph

The OpenMetadata graph does not only store data assets. It stores the relationships between assets, columns, owners, teams, policies, quality tests, lineage, classifications, glossary terms, metrics, domains, data contracts, data products, conversations, and memory nuggets.

Example relationships:

Table               ──hasColumn────────────> Column
Column              ──classifiedAs─────────> PII
Column  

// HOW IT'S BUILT

KEY FILES

skills/openmetadata-workflow/SKILL.mdREADME.md

// REPO STATS

15.4k stars