Name: quickstart
Rating: 69.6 (1 reviews)
Author: databricks

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.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

The body is a strong, highly actionable multi-step workflow with explicit sequencing and error-handling checkpoints. Its main weaknesses are repetition across sections, unfilled {{LAKEBASE_*}} template placeholders that leave a few broken lines, and a monolithic structure with no reference files split out.

Suggestions

Resolve the unfilled {{LAKEBASE_OPTIONS}}, {{LAKEBASE_EXAMPLES}}, {{LAKEBASE_CONFIGURES_ENV}}, and {{LAKEBASE_CONFIGURES_YML}} placeholders (e.g. line 114 renders as a broken option entry) so the rendered content is complete.

De-duplicate the flag reference: the "Run Quickstart" options and "Interactive Prompts" tables restate flags already specified in the Setup Flow — consolidate into one authoritative reference to tighten conciseness.

Move the detailed interactive-prompt tables and manual-auth fallback into a referenced file (e.g. references/interactive-prompts.md) so SKILL.md stays a lean overview and progressive disclosure reaches one-level-deep references.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and does not explain concepts Claude already knows, but it repeats material across sections (the "Run Quickstart" options and "Interactive Prompts" tables restate flags already specified in the Setup Flow) and contains unfilled template placeholders ({{LAKEBASE_OPTIONS}}, {{LAKEBASE_EXAMPLES}}, {{LAKEBASE_CONFIGURES_ENV}}, {{LAKEBASE_CONFIGURES_YML}}) that add noise, so it lands at "mostly efficient but could be tightened" rather than lean level 3.	2 / 3
Actionability	It gives exact commands, concrete flags, per-combination copy-paste examples, and precise AskUserQuestion usage instructions (including the tool's failure mode), matching the fully-executable level-3 anchor.	3 / 3
Workflow Clarity	Steps are explicitly numbered and ordered with a "do not skip any step" sequencing rule, and there is an explicit validation/checkpoint ("If the script exits non-zero, surface its error output to the user verbatim and stop — do not retry blindly") plus an idempotency section, satisfying the clear-sequence-with-validation level-3 anchor.	3 / 3
Progressive Disclosure	No bundle files exist (references/scripts/assets directories absent) and the skill is a single ~260-line monolithic document with content that could be split out (full flag reference, interactive-prompt tables, manual-auth fallback) kept inline; it is well-organized into sections but does not use one-level-deep references, matching the level-2 "content that should be separate is inline" anchor rather than the split-out level 3.	2 / 3
	Total	10 / 12 Passed

Description

90%

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 concise, uses third-person/imperative voice, and pairs a clear capability statement with an explicit numbered trigger list. Its only gap is that the capability half names one general action rather than enumerating the several concrete sub-actions the skill performs.

Dimension	Reasoning	Score
Specificity	The phrase "Set up Databricks agent development environment" names a concrete domain and a single setup action, but does not enumerate multiple distinct concrete actions (e.g. configure auth, provision Lakebase, bind app), so it matches the "names domain and some actions, but not comprehensive" anchor rather than the multi-action level 3.	2 / 3
Completeness	It states what the skill does ("Set up Databricks agent development environment") and provides an explicit numbered "Use when:" trigger list answering when to invoke it, satisfying the level-3 both-what-and-when anchor.	3 / 3
Trigger Term Quality	It lists natural terms users would actually say — "quickstart", "set up", "authenticate", "configure databricks" — giving good coverage of phrasings a user would naturally utter, matching the level-3 anchor.	3 / 3
Distinctiveness Conflict Risk	"Databricks agent development environment" with Databricks-specific triggers carves a clear niche unlikely to fire for unrelated skills, matching the level-3 distinct-triggers anchor.	3 / 3
	Total	11 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: databricks/app-templates
Commit: 2a4c792

Reviewed: 5 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.