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.

64

Quality

76%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/quickstart/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%

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

The skill excels at actionability and workflow clarity with precise, executable steps, conditional branching, and error handling. However, it is significantly over-verbose — information is duplicated across sections (the step-by-step flow, the prompts table, and the options reference all cover the same ground), and the monolithic structure makes it harder to navigate. Trimming redundant sections and splitting reference material into separate files would substantially improve token efficiency.

Suggestions

Remove the 'Interactive Prompts (and How to Skip Them)' tables — they duplicate information already covered in Steps 1-4 and the Options section. Consolidate into a single 'Non-interactive flag reference' table if needed.

Move the 'Manual Authentication (Fallback)' and 'Idempotency' sections into a separate TROUBLESHOOTING.md or REFERENCE.md file, keeping only a one-line reference in the main skill.

Remove the 'Optional: Chat-history Lakebase' section entirely — it restates what Step 3's 'Non-memory templates' subsection already covers.

Clean up template placeholders like {{LAKEBASE_OPTIONS}}, {{LAKEBASE_EXAMPLES}}, {{LAKEBASE_CONFIGURES_ENV}}, and {{LAKEBASE_CONFIGURES_YML}} — they add visual noise and suggest incomplete content.

DimensionReasoningScore

Conciseness

The skill is extremely verbose at ~250+ lines. It repeats information extensively — the interactive prompts table duplicates what's already explained in the Step-by-step flow, the 'Optional: Chat-history Lakebase' section restates what's in Step 3, and the 'What Quickstart Configures' section includes template placeholders ({{LAKEBASE_OPTIONS}}) that add noise. Many sections explain things Claude can infer (e.g., explaining what idempotency means in context, explaining what each prompt does when the flags already make it clear).

1 / 3

Actionability

The skill provides highly concrete, executable guidance with specific CLI commands, exact flag names, example invocations covering multiple scenarios, and clear instructions on which tool to use (AskUserQuestion vs chat message). The step-by-step flow is fully actionable with specific API calls and JSON field references.

3 / 3

Workflow Clarity

The multi-step workflow is clearly sequenced (Steps 1-4) with explicit dependencies between steps, conditional branching clearly marked, error handling (non-zero exit), and validation checkpoints (e.g., checking CLI version, verifying profiles). The flow includes feedback loops like 'if errors, surface verbatim and stop.'

3 / 3

Progressive Disclosure

The skill references other skills ('discover-tools' skill, 'run-locally' skill) in Next Steps, which is good. However, the content is monolithic — the interactive prompts table, manual authentication fallback, idempotency notes, and detailed Lakebase sub-flows could be split into separate reference files. The inline content is overwhelming for what should be an overview-level skill.

2 / 3

Total

9

/

12

Passed

Description

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.

The description is well-structured with a clear 'Use when' clause and good trigger terms that make it easy for Claude to select this skill appropriately. Its main weakness is that the 'what' portion is somewhat thin—it says 'set up' but doesn't enumerate the specific concrete actions involved in the setup process. Overall it's a solid description that would perform well in skill selection.

Suggestions

Expand the 'what' portion to list specific concrete actions, e.g., 'Installs dependencies, creates .env configuration file, sets up Databricks authentication tokens, and validates connectivity.'

DimensionReasoningScore

Specificity

Names the domain (Databricks agent development environment) and the general action (set up), but doesn't list multiple concrete actions beyond setup—e.g., it doesn't specify what setup entails (installing packages, creating config files, generating tokens, etc.).

2 / 3

Completeness

Clearly answers both 'what' (set up Databricks agent development environment) and 'when' with an explicit 'Use when' clause listing four specific trigger conditions.

3 / 3

Trigger Term Quality

Includes strong natural trigger terms users would actually say: 'quickstart', 'set up', 'authenticate', 'configure databricks', '.env file', and 'first time setup'. Good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Highly specific to Databricks agent development environment setup with distinct triggers like 'configure databricks', '.env file', and 'quickstart' in that context. Unlikely to conflict with other skills.

3 / 3

Total

11

/

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.

Validation11 / 11 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.