deploy
Deploy agent to Databricks Apps using DAB (Databricks Asset Bundles). Use when: (1) User says 'deploy', 'push to databricks', or 'bundle deploy', (2) 'App already exists' error occurs, (3) Need to bind/unbind existing apps, (4) Debugging deployed apps, (5) Querying deployed app endpoints.
90
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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.
This is a strong skill description that clearly defines its scope around Databricks Apps deployment using DAB. It excels in providing explicit trigger scenarios including user phrases, error conditions, and specific tasks. The description is concise yet comprehensive, covering both the 'what' and 'when' effectively with distinct, natural trigger terms.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: deploying agents, using DAB (Databricks Asset Bundles), binding/unbinding existing apps, debugging deployed apps, and querying deployed app endpoints. | 3 / 3 |
Completeness | Clearly answers both 'what' (deploy agent to Databricks Apps using DAB) and 'when' with an explicit 'Use when:' clause listing five specific trigger scenarios including user phrases, error conditions, and task types. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would actually say: 'deploy', 'push to databricks', 'bundle deploy', 'App already exists' error, 'bind/unbind', 'debugging deployed apps', 'querying deployed app endpoints'. Good coverage of both common terms and specific error scenarios. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Databricks Apps deployment via DAB. The specific platform (Databricks), tool (DAB/Databricks Asset Bundles), and action (deploy agent) make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 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 deployment skill with excellent workflow clarity and concrete commands throughout. Its main weakness is length — at ~200 lines it packs a lot of content that could benefit from splitting into separate files (e.g., troubleshooting, bind workflow). The content is well-organized with clear headers but could be slightly more concise by trimming explanatory notes that Claude can infer.
Suggestions
Consider moving the 'Handling App Already Exists Error' section (with its two options and multi-step bind workflow) into a separate referenced file to reduce the main skill's length.
Trim explanatory '> Why this matters' callouts — Claude can infer why config must match or why root_path is needed from the error messages alone.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and provides necessary deployment-specific knowledge, but includes some unnecessary explanations (e.g., explaining what OAuth is, explaining why production mode needs root_path when the error message already tells you). Some sections like OBO authentication and FAQ could be tightened. | 2 / 3 |
Actionability | Excellent actionability throughout — every section provides concrete, copy-paste-ready bash commands and YAML configurations. The bind workflow includes specific jq queries, exact CLI commands, and real error messages to match against. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with numbered steps, explicit validation checkpoints (pre-flight check, bundle validate before deploy), and feedback loops (check if already bound before binding, fix-and-retry patterns). The 'App Already Exists' workflow is particularly well-structured with decision points and user prompts. | 3 / 3 |
Progressive Disclosure | The skill references other skills (add-tools, lakebase-setup) and external docs appropriately, but the content itself is quite long and monolithic. The FAQ, troubleshooting table, and detailed bind workflow could potentially be split into separate reference files. However, references that do exist are one-level deep and clearly signaled. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- databricks/app-templates
- Commit
dfeb4ac
- 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.