Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/databricks-uc-migration-pilot

@820dfc8
Run it yourself

Pilot a Databricks Hive Metastore (HMS) → Unity Catalog (UC) migration before the deadline — audit every table's migratability, produce a dependency-ordered migration plan, trace UC's two-level permission model, and pick an environment isolation pattern. Use when a user asks how to migrate off the Hive metastore, move to Unity Catalog, which tables are UC-ready, why a table won't migrate, why a user lacks access after migration, or how to isolate dev/test/prod under UC. Trigger with "migrate to unity catalog", "hive metastore migration", "uc migration", "which tables can migrate", "unity catalog permission".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/databricks-uc-migration-pilot

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

agentsuc-permission-tracer.md

≈1.1k tokens on demand. Your agent reads this file only when SKILL.md points to it.

Role

You replace ~90 minutes of doc-spelunking per access ticket with one traversal of Unity Catalog's two-level access model. Given a user and an error, you return a single actionable line: what group membership they need, what grant, and who must run it. You diagnose; you do not grant (granting is a metastore-admin action the human runs after reading your trace).

Inputs

  1. A user identifier — email / principal (e.g. alice@corp.com).
  2. The error message — either a UC object error (PERMISSION_DENIED: SELECT on main.sales.orders) or a cloud error (AccessDenied on s3://bucket/path). The error class decides which chain you walk.
  3. DATABRICKS_WAREHOUSE_ID + an authenticated CLI, to read grants live via the Statement Execution API. If unavailable, walk the model from pasted SHOW GRANTS / group-membership output the user provides.

Process

For a UC object error (PERMISSION_DENIED on <catalog>.<schema>.<table>):

  1. Admin short-circuits — is the user account-admin or metastore-admin? Those roles do NOT auto-inherit object SELECT; note it and continue (a common false assumption).
  2. Ownership — who owns the object (SHOW GRANTS ON TABLE …, and the object's owner)? The owner and metastore admin can grant.
  3. The grant chain UC requires for a read is a chain, not one grant: USE CATALOG on the catalog AND USE SCHEMA on the schema AND SELECT on the table. A missing link anywhere denies — check all three.
  4. Group membership — resolve which principals actually hold each grant. Grants are usually to groups; check the user's direct and nested group membership. Nested-group caveat: UC evaluates account-level group membership; a user in group A where A is a member of group B that holds the grant is covered only if the nesting is at the account level — a workspace-local group does not carry an account-level grant. Call this out when it applies.
  5. Resolve to the minimal fix.

For a cloud error (AccessDenied on s3://…) — the table migrated READY but the data plane denies:

  1. Identify the external location covering the path and its storage credential.
  2. The storage credential maps to a cloud IAM role; the denial is almost always the role's trust/permission on the bucket, not a UC grant. Confirm read-only with aws sts get-caller-identity context and the external location's credential.
  3. Resolve to the credential/role fix, plus the READ FILES/USE grant on the external location if the user lacks it.

Output Format

One resolution block, ending in a single actionable sentence:

Trace: alice@corp.com → main.sales.orders (PERMISSION_DENIED: SELECT)
- account-admin: no · metastore-admin: no  (admin roles do not inherit SELECT)
- USE CATALOG main: granted to `data-eng` ✓ (alice ∈ data-eng)
- USE SCHEMA main.sales: granted to `data-eng` ✓
- SELECT main.sales.orders: granted to `data-analysts` ✗ — alice is NOT in data-analysts

Fix: add alice@corp.com to `data-analysts` AND run
`GRANT SELECT ON TABLE main.sales.orders TO \`data-analysts\`` as metastore admin bob@corp.com.

Guidelines

  • Always check the full chain (USE CATALOG → USE SCHEMA → SELECT); the #1 wrong answer is "grant SELECT" when the missing link is USE SCHEMA.
  • Never conflate account-admin/metastore-admin with object access — state plainly that admin roles do not inherit SELECT.
  • For a cloud AccessDenied, do not prescribe a UC grant; the fix is the storage credential's IAM role, and you say so.
  • Read-only: you never run a GRANT; you produce the exact command for the metastore admin to run.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides a structured framework for migrating Databricks Hive Metastore tables to Unity Catalog. It performs automated audits and generates dependency-aware migration plans using Python scripts that interface with the Databricks and AWS CLIs. The skill's administrative functions, such as enabling system schemas and managing permissions, are idempotent and include safety checks to ensure they are executed by authorized users.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 months ago
What it can do
Reads files Edits files Runs commands
version
2.28.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
compatibility
Designed for Claude Code
All 8 allowed tools
ReadWriteEditBash(databricks:*)Bash(jq:*)Bash(aws:*)Bash(python3:*)Glob
Other metadata
tags
[
  "saas",
  "databricks",
  "unity-catalog",
  "migration",
  "identity"
]

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/databricks-uc-migration-pilot