Unity Catalog And Lakehouse Governance

Community

vaquarkhan

unity-catalog-and-lakehouse-governance

Guides agents through Unity Catalog governance workflows for Databricks lakehouses. Use when defining catalogs, schemas, external locations, access boundaries, shares, lineage, and cross-workspace governance for governed Delta Lake, ML, analytics, and serving assets.

Overview

Publisher	vaquarkhan
Repository	`data-engineering-agent-skills`
Skill name	`unity-catalog-and-lakehouse-governance`
Stars	60
Forks	8
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by vaquarkhan on GitHub. Read the source before you install it.

Installation

Install the Unity Catalog And Lakehouse Governance AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/vaquarkhan/data-engineering-agent-skills/tree/main/skills/unity-catalog-and-lakehouse-governance
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/vaquarkhan/data-engineering-agent-skills/tree/main/skills/unity-catalog-and-lakehouse-governance

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/vaquarkhan/data-engineering-agent-skills.git /tmp/data-engineering-agent-skills
mkdir -p .claude/skills
cp -r /tmp/data-engineering-agent-skills/skills/unity-catalog-and-lakehouse-governance .claude/skills/unity-catalog-and-lakehouse-governance

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Unity Catalog And Lakehouse Governance in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Unity Catalog And Lakehouse Governance on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Unity Catalog And Lakehouse Governance is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Unity Catalog And Lakehouse Governance

Overview

Use this skill when Unity Catalog is the core governance surface for a Databricks platform. It helps agents design governed boundaries across catalogs, schemas, storage locations, shares, and access paths for lakehouse data products.

When to Use

designing Unity Catalog hierarchy and ownership
defining external locations, credentials, and storage boundaries
governing shared Delta tables, views, volumes, or models
reviewing cross-workspace or multi-team lakehouse governance
planning secure sharing, publish approvals, or governed consumer access

Do not reduce Unity Catalog to permissions only. It is also a publish, ownership, and operating-boundary decision.

Workflow

Define the governance hierarchy. Decide:
- catalog boundaries
- schema boundaries
- producer versus consumer separation
- ownership and stewardship paths
Define storage and credential boundaries. Cover:
- external locations
- managed versus external tables
- storage credentials
- workspace and environment separation
Define access and sharing behavior. Include:
- roles and groups
- row or column restrictions where needed
- governed views
- cross-team or external sharing expectations
Align governance with lakehouse delivery. Require:
- clear publish layers
- lineage visibility
- certification or trust signals
- handling for schema and contract change
Validate day-2 operations. Review how promotions, new workspaces, external consumers, and object-store boundaries behave under the governance model.

Common Rationalizations

Rationalization	Reality
"We already use Databricks, so Unity Catalog design is obvious."	Poor catalog and location design creates long-term friction in ownership, sharing, and environment boundaries.
"We can give broad workspace access and tighten later."	Over-broad access becomes hard to unwind once shared data products are adopted.
"Lineage comes for free."	Platform lineage is useful only when publish boundaries and ownership are designed intentionally.

Red Flags

catalogs and schemas do not map to ownership or publish boundaries
external locations and credentials are inconsistent or ad hoc
workspace separation and environment promotion are vague
sharing or external-consumer behavior is undocumented
governed lakehouse objects are published without trust or lineage signals

Verification

Catalog, schema, and ownership boundaries are intentional
Storage and credential boundaries are explicit
Access and sharing rules fit the consumer model
Publish and lineage expectations are visible
Promotions and day-2 operations work with the governance design

Frequently asked questions

What does the Unity Catalog And Lakehouse Governance AI skill do?

Why use Unity Catalog And Lakehouse Governance on TypingMind?

Because you install it once and use it with any model. Unity Catalog And Lakehouse Governance is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Unity Catalog And Lakehouse Governance in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/vaquarkhan/data-engineering-agent-skills/tree/main/skills/unity-catalog-and-lakehouse-governance. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Unity Catalog And Lakehouse Governance?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Unity Catalog And Lakehouse Governance?

As many as you like. As long as a model supports skills, you can use Unity Catalog And Lakehouse Governance with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Unity Catalog And Lakehouse Governance AI skill free?

Yes. It is published on GitHub by vaquarkhan under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

1password

openclaw

OrganizationPopular

Set up and use 1Password CLI for sign-in, desktop integration, and reading or injecting secrets.

Apple Reminders

List, add, edit, complete, or delete Apple Reminders and reminder lists via remindctl.

Clawhub

Search ClawHub for skills when a requested capability is not already available; install, verify, update, uninstall, publish, or sync skills.

Diagnosing Superpowers

obra

CommunityPopular

Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Unity Catalog And Lakehouse Governance

Overview

When to Use

Workflow

Common Rationalizations

Red Flags

Verification

Frequently asked questions

Related AI Skills

Set up your own AI workspace now