databricks-upgrade-migration
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill databricks-upgrade-migrationUpgrade Databricks runtime versions and migrate between features. Use when upgrading DBR versions, migrating to Unity Catalog, or updating deprecated APIs and features. Trigger with phrases like "databricks upgrade", "DBR upgrade", "databricks migration", "unity catalog migration", "hive to unity".
Validation
75%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
Implementation
65%This is a comprehensive migration skill with strong actionability through executable Python and SQL code. However, it's verbose for a skill file and lacks explicit validation checkpoints critical for migration operations. The content would benefit from being split into a concise overview with references to detailed migration scripts.
Suggestions
Add explicit validation checkpoints between migration steps (e.g., 'STOP: Verify table count matches before proceeding to permissions')
Move detailed Python scripts to separate files (e.g., scripts/migrate_to_unity_catalog.py) and reference them from the skill
Remove placeholder code like 'pass' statements and incomplete library checking loops that add no value
Add rollback procedures for failed migrations, especially for the destructive Unity Catalog migration steps
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary elements like the placeholder 'pass' statements, empty library checking loops, and verbose comments explaining obvious things. The version compatibility matrix and error handling table add value, but some sections could be tightened. | 2 / 3 |
Actionability | Provides fully executable Python code and SQL commands with clear function signatures, docstrings, and concrete examples. The migration scripts are copy-paste ready with proper error handling and return types. | 3 / 3 |
Workflow Clarity | Steps are numbered and sequenced (Steps 1-4), but validation checkpoints are implicit rather than explicit. The migration runbook at the end shows a validation step, but the main migration scripts lack explicit 'validate before proceeding' gates for these destructive/batch operations. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is quite long (~250 lines) with detailed code that could be split into separate reference files. The Resources section provides external links, but internal references to separate detailed docs would improve navigation. | 2 / 3 |
Total | 9 / 12 Passed |
Activation
90%This is a well-structured skill description with strong trigger term coverage and explicit guidance on when to use it. The main weakness is that the specific capabilities could be more detailed - it mentions upgrading and migrating but doesn't enumerate the concrete actions performed (e.g., 'updates spark configurations', 'rewrites legacy table references').
Suggestions
Expand the capabilities list with more specific actions like 'updates Spark configurations', 'rewrites legacy Hive metastore references', or 'converts deprecated DataFrame APIs' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Databricks) and some actions ('upgrade runtime versions', 'migrate between features'), but lacks comprehensive specific actions like what exactly happens during migration or what deprecated APIs are handled. | 2 / 3 |
Completeness | Clearly answers both what (upgrade runtime versions, migrate to Unity Catalog, update deprecated APIs) and when (explicit 'Use when' clause plus 'Trigger with phrases' providing concrete examples). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'databricks upgrade', 'DBR upgrade', 'databricks migration', 'unity catalog migration', 'hive to unity' - these are realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche with Databricks-specific terminology (DBR, Unity Catalog, hive to unity) that would not conflict with general database or migration skills. | 3 / 3 |
Total | 11 / 12 Passed |
Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.