databricks-unity-catalog

Manage Unity Catalog catalogs, schemas, and tables with governance and naming conventions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/andregit2026/Databricks_DQ_Business --skill databricks-unity-catalog-andregit2026
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: databricks-unity-catalog
Source: https://github.com/andregit2026/Databricks_DQ_Business/tree/main/.claude/skills/databricks-general-skill-unity-catalog
Command: npx skills add https://github.com/andregit2026/Databricks_DQ_Business --skill databricks-unity-catalog-andregit2026

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unity Catalog management often requires consistent, governed creation and maintenance of catalogs, schemas, and tables across environments, which can be error-prone without a standard workflow.

Core Features & Use Cases

  • Explore catalogs, schemas, and tables to understand structure and ownership.
  • Create and update schemas and tables with governance, naming conventions, and ownership enforcement.
  • Validate metadata and perform safe deletions with confirm prompts integrated into MCP-driven workflows.

Quick Start

Use the Unity Catalog skill to discover catalogs and create a new schema under a target catalog, ensuring naming and governance standards are applied.

Frequently Asked Questions about databricks-unity-catalog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage Databricks Unity Catalog resources across environments?

Manage Databricks Unity Catalog resources using standardized workflows for discovery, creation, updates, and deletion. This enforces three-level naming, owner assignment, and safe CRUD operations to maintain consistent governance across catalogs, schemas, and tables.

What is the best way to create schemas in Databricks Unity Catalog with proper naming conventions?

Create schemas in Databricks Unity Catalog by applying enforced naming conventions and governance standards. The workflow validates catalog and schema metadata while assigning ownership during creation to ensure standardized resource management.

Does Databricks Unity Catalog support safe deletion workflows for tables and schemas?

Databricks Unity Catalog supports safe deletions for tables and schemas using confirmation prompts integrated into MCP-driven workflows. This prevents accidental data loss while validating metadata before removing resources.

Can I discover and validate ownership for existing catalogs and tables in Databricks Unity Catalog?

Discover existing catalogs, schemas, and tables in Databricks Unity Catalog to understand their structure and ownership. The workflow validates metadata across all three levels to ensure governance compliance.

Why do I need three-level naming for Databricks Unity Catalog table management?

Three-level naming for Databricks Unity Catalog table management enforces consistent identification across catalogs, schemas, and tables. This standardization prevents naming conflicts and ensures proper governance in production environments.

What are the limitations of using MCP tools for Unity Catalog governance workflows?

MCP tools for Unity Catalog governance workflows require valid metadata across catalogs, schemas, and tables. Operations fail if naming conventions or ownership assignments do not meet validation standards in production Databricks environments.