CtrlK
BlogDocsLog inGet started
Tessl Logo

databricks-pipelines

Develop Lakeflow Spark Declarative Pipelines (formerly Delta Live Tables) on Databricks. Use when building batch or streaming data pipelines with Python or SQL. Invoke BEFORE starting implementation.

71

Quality

87%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

This is a high-quality, well-structured skill that serves as an effective hub for Lakeflow Declarative Pipelines development. Its greatest strengths are the decision tree for dataset type selection, the concrete error/fix mappings, and the excellent progressive disclosure to reference files. The main weakness is that the extensive API reference tables, while useful, add significant token weight and could potentially be moved to a separate reference file to keep the main skill leaner.

Suggestions

Consider moving the large API reference tables (Dataset Definition, Flow/Sink, CDC, Data Quality, Reading Data, Table/Schema Features) into a separate `api-reference.md` file and linking to it, keeping only the most critical 1-2 tables inline to reduce token cost.

DimensionReasoningScore

Conciseness

The skill is dense and comprehensive but could be tightened. The API reference tables are extensive and somewhat redundant (repeating the same reference file links across many rows). The decision tree and common traps sections are efficient, but the sheer volume of tables — especially the legacy migration table and the reading data APIs — pushes toward verbosity. However, it avoids explaining basic concepts Claude already knows.

2 / 3

Actionability

The skill provides highly concrete, actionable guidance: exact CLI commands for running pipelines, specific API names and decorators, precise error-to-fix mappings, and clear decision trees. Code snippets are executable (e.g., `databricks bundle deploy -t dev --profile <profile>`), and the legacy migration table gives exact before/after patterns.

3 / 3

Workflow Clarity

Multi-step workflows are clearly sequenced with explicit validation checkpoints. The 'Running a Pipeline' section has ordered steps (validate → deploy → run → check status), warns about destructive operations (full refresh data loss), requires explicit user approval for dangerous actions, and mandates polling the update rather than top-level state. The three workflow choices (A, B, C) are clearly delineated with decision criteria.

3 / 3

Progressive Disclosure

The skill is an excellent overview that delegates detailed content to well-organized reference files. References are one level deep, clearly signaled with markdown links, and organized by feature and language in structured tables. The Reference Index at the bottom provides a clean navigation map. Content is appropriately split between the main skill (decision trees, common traps, workflow selection) and detailed references.

3 / 3

Total

11

/

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.

This is a solid description with excellent trigger term coverage (including the former product name), clear 'when' guidance, and a highly distinctive niche. Its main weakness is the lack of specific concrete actions — it says 'develop' but doesn't enumerate what specific tasks it helps with (e.g., defining streaming tables, setting expectations, configuring pipelines).

Suggestions

Add 2-3 specific concrete actions to improve specificity, e.g., 'Define streaming tables, materialized views, and data quality expectations in Lakeflow Spark Declarative Pipelines.'

DimensionReasoningScore

Specificity

The description names the domain (Lakeflow Spark Declarative Pipelines / Delta Live Tables on Databricks) and mentions batch/streaming data pipelines with Python or SQL, but does not list specific concrete actions like 'create tables', 'define expectations', 'configure materialized views', etc.

2 / 3

Completeness

Clearly answers both 'what' (develop Lakeflow Spark Declarative Pipelines on Databricks) and 'when' ('Use when building batch or streaming data pipelines with Python or SQL. Invoke BEFORE starting implementation.'). The explicit 'Use when' clause with timing guidance is well done.

3 / 3

Trigger Term Quality

Includes strong natural trigger terms: 'Lakeflow', 'Spark Declarative Pipelines', 'Delta Live Tables', 'Databricks', 'batch', 'streaming', 'data pipelines', 'Python', 'SQL'. The inclusion of the former name 'Delta Live Tables' is especially helpful since many users will still use that term.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive — targets a very specific Databricks technology (Lakeflow Spark Declarative Pipelines / Delta Live Tables) which is unlikely to conflict with general Python, SQL, or data engineering skills. The niche is clearly carved out.

3 / 3

Total

11

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

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.