databricks-deploy-integration

Deploy Databricks jobs and pipelines with Declarative Automation Bundles. Use when deploying jobs to different environments, managing deployments, or setting up deployment automation. Trigger with phrases like "databricks deploy", "asset bundles", "databricks deployment", "deploy to production", "bundle deploy".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong, highly actionable skill body with executable commands, complete configs, and a well-sequenced promotion workflow including validation checkpoints. Its main weakness is progressive disclosure: everything lives inline in one long file with no reference files to offload the detailed configuration examples.

Suggestions

Move the large resource-definition examples (jobs.yml, pipelines.yml, permissions block) into files under references/ and link to them from a concise overview, reducing the inline SKILL.md length.

Extract the Error Handling table and detailed deploy-lifecycle commands into a reference file, keeping only the core workflow and promotion steps inline.

Consider a short 'Quick start' section at the top with the minimal init/configure/deploy path, deferring the multi-environment and permissions depth to reference files.

Dimension	Reasoning	Score
Conciseness	Body is lean and actionable — concrete YAML configs and bash commands dominate, with only a brief domain-specific Overview rather than explanations of concepts Claude already knows; nearly every token earns its place.	3 / 3
Actionability	Provides fully executable, copy-paste-ready commands (e.g. `databricks bundle validate -t staging`, `databricks bundle deploy -t prod`) and complete YAML resource definitions rather than pseudocode.	3 / 3
Workflow Clarity	Steps 1–6 are clearly sequenced, and Step 5 (staging→prod promotion) includes explicit validation checkpoints ("Validate staging is clean", "After staging passes", "Verify production deployment") with an error-handling table and destroy warnings for risky operations.	3 / 3
Progressive Disclosure	Well-organized with clear sections, but the SKILL.md is a ~250-line monolith with large inline config blocks (jobs.yml, pipelines.yml, permissions) that could be split into reference files; no bundle files exist to offload detail, so content that should be separate remains inline.	2 / 3
	Total	11 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is well-constructed: third-person voice, concrete capabilities, explicit "Use when" triggers, and a distinct Databricks-bundles niche. It cleanly satisfies the what/when/trigger requirements with no over-claims or fluff.

Dimension	Reasoning	Score
Specificity	Lists concrete actions — "Deploy Databricks jobs and pipelines" plus "deploying jobs to different environments, managing deployments, or setting up deployment automation" — naming multiple specific capabilities rather than vague language.	3 / 3
Completeness	Explicitly answers both what ("Deploy Databricks jobs and pipelines with Declarative Automation Bundles") and when ("Use when deploying jobs to different environments...") with explicit trigger guidance.	3 / 3
Trigger Term Quality	Provides natural phrases users would say — "databricks deploy", "asset bundles", "databricks deployment", "deploy to production", "bundle deploy" — with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (Databricks Declarative Automation Bundles) with distinct, domain-specific triggers unlikely to collide with other skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 02d6341

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.