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".
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description that clearly identifies its niche (Databricks deployment with Declarative Automation Bundles), provides explicit 'Use when' guidance, and lists natural trigger phrases. The main weakness is that the capability description could be more specific about the concrete actions beyond 'deploy jobs and pipelines'—e.g., mentioning environment configuration, bundle validation, or workspace setup.
Suggestions
Expand the capability list with more concrete actions, e.g., 'configure bundle YAML, validate bundles, promote across dev/staging/prod environments, manage workspace settings'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Databricks) and some actions (deploy jobs and pipelines, Declarative Automation Bundles), but doesn't list multiple concrete actions comprehensively—e.g., doesn't mention configuration, testing, rollback, or monitoring of deployments. | 2 / 3 |
Completeness | Clearly answers both 'what' (deploy Databricks jobs and pipelines with Declarative Automation Bundles) and 'when' (deploying jobs to different environments, managing deployments, setting up deployment automation), with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'databricks deploy', 'asset bundles', 'databricks deployment', 'deploy to production', 'bundle deploy'. These cover common variations a user would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Databricks deployment with Declarative Automation Bundles—unlikely to conflict with generic deployment or CI/CD skills due to the Databricks-specific terminology and trigger terms. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable skill with excellent workflow clarity and real-world deployment patterns. The step-by-step progression from initialization through production promotion is well-sequenced with proper validation gates. The main weakness is length — the comprehensive YAML examples, while useful, make this a heavy skill that could benefit from splitting detailed resource definitions into referenced files.
Suggestions
Consider moving the detailed resource YAML examples (jobs.yml, pipelines.yml) into a separate referenced file like RESOURCES_EXAMPLES.md to reduce the main skill's token footprint.
Remove the Output section as it merely restates what the skill already demonstrates through its examples.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some unnecessary verbosity like the Output section that just restates what was already shown, and some comments that explain obvious things. The error handling table and examples are useful but the overall length could be tightened. | 2 / 3 |
Actionability | Excellent actionability with fully executable bash commands and complete YAML configurations that are copy-paste ready. Every step includes concrete, specific code examples with realistic values and proper variable interpolation. | 3 / 3 |
Workflow Clarity | Clear 6-step sequential workflow with explicit validation checkpoints (validate before deploy, test staging before promoting to prod). Step 5 includes a proper feedback loop: validate → deploy → run → check result → promote. The destroy command is explicitly scoped to dev only with warnings. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and logical sections, but it's quite long (~180 lines of substantive content) and could benefit from splitting resource definitions and the promotion workflow into separate referenced files. The Resources section at the end provides good external links but inline content is heavy. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
70e9fa4
- 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.