CtrlK
BlogDocsLog inGet started
Tessl Logo

quickstart

Set up Databricks agent development environment. Use when: (1) First time setup, (2) Configuring Databricks authentication, (3) User says 'quickstart', 'set up', 'authenticate', or 'configure databricks', (4) No .env file exists.

69

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is quickstart in databricks/app-templates

SKILL.md
Quality
Evals
Security

Quality

Content

81%Weight 40%Scale 1-5

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

A highly actionable, well-sequenced setup skill with explicit validation and error handling. Main weakness is conciseness — duplicated example blocks and restated flag information could be consolidated, and some inline sections could move to references.

Suggestions

Consolidate the duplicate `uv run quickstart` example blocks: keep one set under 'Run Quickstart' and have Step 4 reference it rather than restating full commands.

Move the 'Interactive Prompts (and How to Skip Them)' tables and 'Manual Authentication (Fallback)' into a references file and link to them from the main flow to reduce inline length.

Tighten the flag descriptions in 'Run Quickstart > Options' so they are not repeated verbatim in the interactive-prompt skip tables.

DimensionReasoningScore

Conciseness

Mostly efficient and dense, but the quickstart command examples are repeated across 'Step 4' and 'Run Quickstart', and the interactive-prompt tables restate flag info already given; could be tightened.

3 / 5

Actionability

Fully executable: concrete commands, exact flags, exact AskUserQuestion option text, API calls, and copy-paste-ready example invocations covering the common cases.

5 / 5

Workflow Clarity

Explicitly ordered 4-step sequence with stated step dependencies, plus an explicit validation checkpoint ('If the script exits non-zero, surface its error output verbatim and stop') and error-recovery guidance.

5 / 5

Progressive Disclosure

Well-organized with clear section headers and no nested references, but no bundle/reference files exist and sizable material (interactive prompt tables, manual auth fallback) is inlined rather than split out.

4 / 5

Total

17

/

20

Passed

Description

87%Weight 40%Scale 1-5

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

A strong, specific description that answers both 'what' and 'when' with explicit user-facing trigger phrases and a clear Databricks niche. Minor room to broaden trigger synonyms and action coverage.

DimensionReasoningScore

Specificity

Names the domain and concrete actions ('Set up Databricks agent development environment', 'Configuring Databricks authentication') with minor coverage gaps; not the comprehensive multi-action list of a 5.

4 / 5

Completeness

Clearly states what ('Set up Databricks agent development environment') and an explicit 'Use when:' clause with four concrete trigger conditions.

5 / 5

Trigger Term Quality

Includes natural user-facing terms ('quickstart', 'set up', 'authenticate', 'configure databricks') plus contextual triggers; a few synonyms/extensions missing for a 5.

4 / 5

Distinctiveness Conflict Risk

Databricks-specific domain and Databricks-scoped trigger terms create a clear niche with minimal conflict risk; uses third-person imperative voice.

5 / 5

Total

18

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
databricks/app-templates
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.