databricks-local-dev-loop
Configure Databricks local development with Databricks Connect, Asset Bundles, and IDE. Use when setting up a local dev environment, configuring test workflows, or establishing a fast iteration cycle with Databricks. Trigger with phrases like "databricks dev setup", "databricks local", "databricks IDE", "develop with databricks", "databricks connect".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/databricks-pack/skills/databricks-local-dev-loop/SKILL.mdQuality
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 with excellent trigger term coverage and completeness, clearly answering both what and when. Its main weakness is that the specificity of concrete actions could be improved—it describes the general purpose (configure/set up) but doesn't enumerate the specific tasks performed. The explicit trigger phrases and Databricks-specific terminology make it highly distinctive.
Suggestions
Add more specific concrete actions beyond 'configure', such as 'install Databricks Connect, set up authentication profiles, configure cluster connections, initialize Asset Bundle projects, and integrate with VS Code or PyCharm'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Databricks local development) and some specific tools (Databricks Connect, Asset Bundles, IDE), but doesn't list multiple concrete actions beyond 'configure' and 'setting up'. It lacks detail on what specific tasks are performed (e.g., install dependencies, configure authentication, set up cluster connections). | 2 / 3 |
Completeness | Clearly answers both 'what' (configure Databricks local development with Connect, Asset Bundles, and IDE) and 'when' (setting up local dev environment, configuring test workflows, establishing fast iteration cycle) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases like 'databricks dev setup', 'databricks local', 'databricks IDE', 'develop with databricks', 'databricks connect'. Also includes terms like 'local dev environment', 'test workflows', and 'fast iteration cycle' which users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Databricks local development setup with distinct trigger terms like 'databricks connect', 'databricks IDE', and 'asset bundles'. Very unlikely to conflict with other skills given the narrow, well-defined niche. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, highly actionable skill with complete executable examples covering the full Databricks local dev setup. Its main weaknesses are length (could benefit from splitting detailed configs into referenced files) and missing validation checkpoints between setup steps that would help catch configuration errors early. The error handling table is a nice touch but doesn't compensate for the lack of inline verification gates in the workflow.
Suggestions
Add explicit validation checkpoints between steps, e.g., 'Verify: run `databricks-connect test` — only proceed to Step 4 if this succeeds' and 'Run `databricks bundle validate` — fix any errors before deploying'.
Move the detailed Asset Bundle YAML configs and VS Code settings into separate referenced files (e.g., BUNDLE_CONFIG.md, IDE_SETUP.md) to reduce the main skill's token footprint.
Trim the overview paragraph and inline comments that explain concepts Claude already knows (e.g., what Databricks Connect does, what bronze/silver/gold layers are).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some unnecessary commentary (e.g., explaining what Databricks Connect does in the overview, comments like '# Results streamed back locally'). The project structure section is quite verbose and could be trimmed. Overall reasonably lean but not maximally token-efficient. | 2 / 3 |
Actionability | Fully executable code throughout — bash commands, Python code, YAML configs, and VS Code settings are all copy-paste ready. Specific version numbers, concrete file paths, and complete working examples make this highly actionable. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (Steps 1-7) and the dev workflow commands are well-organized. However, there are no explicit validation checkpoints or feedback loops between steps — e.g., no 'verify Connect works before proceeding to Step 4' or 'if bundle validate fails, fix before deploying'. The `databricks-connect test` command is mentioned but not framed as a gate. For a multi-step setup process, this lacks error recovery guidance between steps. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections, but it's quite long and monolithic — the Asset Bundle config, test setup, and VS Code config could be split into separate reference files. There's a good reference to 'databricks-sdk-patterns' at the end and external docs in Resources, but the main file tries to contain everything inline. | 2 / 3 |
Total | 9 / 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.