CtrlK
BlogDocsLog inGet started
Tessl Logo

databricks-jobs

Develop and deploy Lakeflow Jobs on Databricks via DABs, Python SDK, or the CLI. Use when creating data engineering jobs with notebooks, Python wheels, SQL, dbt, or pipelines. Invoke BEFORE starting implementation.

73

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

The content is highly actionable with executable examples across DABs, SDK, and CLI, and uses progressive disclosure effectively via real reference files. The main gaps are a slightly long inline template block and the absence of an explicit validation feedback loop in the development workflow.

Suggestions

Add an explicit feedback loop to the Development Workflow: after `bundle validate`, state 'If validation fails, fix errors and re-validate before deploying'.

Move the inline CLAUDE.md/AGENTS.md template into a reference file (e.g. references/project-scaffolding.md) and link to it, trimming the SKILL.md body.

Tighten the run_if and permission-level enumerations by linking to the relevant reference sections instead of fully inlining both the list and the examples.

DimensionReasoningScore

Conciseness

The body is dense and mostly assumes Claude's competence — it avoids explaining what Databricks or jobs are — but the inline CLAUDE.md/AGENTS.md template block and some enumerations (run_if, permission levels) could be trimmed slightly.

4 / 5

Actionability

Provides copy-paste-ready code and commands across all three interfaces (DABs YAML, Python SDK, CLI) for quick start, common operations, compute, parameters, and permissions, covering the common cases.

5 / 5

Workflow Clarity

The Development Workflow lists Validate → Deploy → Run → Check status with concrete commands, and validation is present, but there is no explicit 'only proceed when valid' feedback loop or error-recovery checkpoint for these batch/deploy operations.

4 / 5

Progressive Disclosure

SKILL.md is a well-signaled overview with a reference table and two summary tables linking to four one-level-deep reference files; all referenced files exist and their section anchors resolve to real headings.

5 / 5

Total

18

/

20

Passed

Description

96%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.

The description is concise, third-person, and explicitly covers what the skill does and when to use it, with strong natural trigger terms. The only weakness is slight overlap with the sibling databricks-pipelines skill via the 'pipelines' trigger term.

DimensionReasoningScore

Specificity

Names the domain and multiple concrete actions — 'Develop and deploy Lakeflow Jobs on Databricks via DABs, Python SDK, or the CLI' — and enumerates five task types (notebooks, Python wheels, SQL, dbt, pipelines) plus three interfaces, giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both 'what' (develop and deploy Lakeflow Jobs via DABs/SDK/CLI) and 'when' (use when creating data engineering jobs with the listed task types), plus a timing cue ('Invoke BEFORE starting implementation').

5 / 5

Trigger Term Quality

'Use when creating data engineering jobs with notebooks, Python wheels, SQL, dbt, or pipelines' covers the natural terms users would say, including the main task-type synonyms; DABs is also named.

5 / 5

Distinctiveness Conflict Risk

'Lakeflow Jobs on Databricks' is a clear niche, but the trigger term 'pipelines' overlaps with the related databricks-pipelines skill, creating minor conflict risk with closely related skills.

4 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
databricks/databricks-agent-skills
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.