CtrlK
BlogDocsLog inGet started
Tessl Logo

databricks-apps

Build apps on Databricks Apps platform. Use when asked to create dashboards, data apps, analytics tools, or visualizations. Invoke BEFORE starting implementation.

70

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

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.

A well-structured, highly actionable skill body that uses tables, concrete commands, and one-level-deep references to keep the overview lean while routing detail to bundle files. The main weakness is redundancy of the app-naming rule across three sections, which slightly hurts token efficiency.

Suggestions

State the app-naming constraint (≤26 chars, lowercase letters/numbers/hyphens, dev- prefix allowance) once in Generic Guidelines and reference it from the Scaffolding and Directory Naming sections instead of restating it three times.

In the 'Required Reading by Phase' table, make the Scaffolding row a brief pointer to the detailed AppKit section rather than re-summarizing the manifest/init --features/--set flow inline.

DimensionReasoningScore

Conciseness

The body is mostly dense and actionable, but the app-naming rule (≤26 chars, lowercase/hyphens) is restated in three places (Generic Guidelines, App Manifest and Scaffolding, and Directory Naming), and the manifest/init scaffolding guidance is summarized in the phase table and then repeated in detail in the AppKit section.

2 / 3

Actionability

Provides concrete, copy-paste-ready commands throughout (`databricks apps manifest`, `databricks apps init --name ... --features ... --set ...`, `npm run typegen`, `databricks apps validate`, `npx @databricks/appkit docs`) plus explicit WRONG/CORRECT scaffolding examples.

3 / 3

Workflow Clarity

The "Development Workflow (FOLLOW THIS ORDER)" section gives a numbered 1–6 sequence with explicit verification checkpoints ("verify all queries show ✓", `databricks apps validate`) and ordering warnings ("DO NOT write UI code before running typegen"); scaffolding has its own manifest-first sequence.

3 / 3

Progressive Disclosure

The body is a concise overview that points to one-level-deep references (references/appkit/*.md, references/platform-guide.md, references/other-frameworks.md, references/testing.md), all verified to exist, organized via a 'Required Reading by Phase' table that signals when to consult each file.

3 / 3

Total

11

/

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.

A strong, third-person description that clearly states both the capability and the explicit trigger conditions, with natural user-facing terms and a distinct platform niche. Its only weakness is that the listed actions are variations of building/creating rather than genuinely distinct operations.

DimensionReasoningScore

Specificity

Names the domain ("Databricks Apps platform") and several app types ("dashboards, data apps, analytics tools, or visualizations"), but the only true action verbs are "Build apps" and "create", which are variations of one operation rather than distinct concrete actions like extract/fill/merge; "apps on Apps platform" is also slightly circular.

2 / 3

Completeness

Explicitly answers both what ("Build apps on Databricks Apps platform") and when ("Use when asked to create dashboards, data apps, analytics tools, or visualizations") via an explicit 'Use when...' trigger clause.

3 / 3

Trigger Term Quality

"Use when asked to create dashboards, data apps, analytics tools, or visualizations" provides good coverage of natural terms a user would actually say when they need this skill.

3 / 3

Distinctiveness Conflict Risk

The Databricks Apps platform is a clear niche with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 10 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 10 deeper-than-1-level

Warning

Total

13

/

16

Passed

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