databricks-hello-world

Create a minimal working Databricks example with cluster and notebook. Use when starting a new Databricks project, testing your setup, or learning basic Databricks patterns. Trigger with phrases like "databricks hello world", "databricks example", "databricks quick start", "first databricks notebook", "create cluster".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

92%

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

A tight, highly actionable tutorial with clear sequencing and built-in verification plus an error-recovery table; its main gap is the absence of any progressive-disclosure structure, keeping everything in one file.

Suggestions

Move the Examples section and/or the per-step code into references/ files (e.g. EXAMPLES.md, scripts/) and link to them from SKILL.md so the overview stays scannable.

Add an explicit 'only proceed when the cluster reports RUNNING' checkpoint between Step 1 and Step 2 to make the implicit gating explicit.

Consider whether the deprecated banner belongs in the skill body or should live in the pack README to avoid spending the skill's token budget on migration notices.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it never explains what Databricks, Delta, or the SDK are — and inline comments (e.g. blocking behavior, cost per DBU) are operational details that earn their tokens rather than padding.	3 / 3
Actionability	Every step ships complete, executable code or CLI commands with real parameter values and expected outputs, making it copy-paste ready.	3 / 3
Workflow Clarity	Five steps are clearly sequenced, Step 5 is an explicit verification pass, and the Error Handling table provides error-to-solution feedback loops for recovery.	3 / 3
Progressive Disclosure	The skill is a well-sectioned but monolithic ~225-line single file with no bundle files (references/scripts/assets absent) and no offloaded reference paths, so content that could be split (Examples, long code blocks) stays inline.	2 / 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 well-structured description with explicit trigger phrases and a clear what/when pairing; its only weakness is that the capability list ('cluster and notebook') is narrower than what the body actually teaches.

Suggestions

Broaden the capability clause to reflect the body's full scope, e.g. 'Create a Databricks cluster, upload and run a notebook, spin up a SQL warehouse, and run a Delta Lake smoke test'.

Dimension	Reasoning	Score
Specificity	It names the domain and two concrete actions ('cluster and notebook'), but under-claims relative to the body (which also covers SQL warehouses, jobs, and Delta), so it is not comprehensive enough for a 3.	2 / 3
Completeness	It explicitly answers both what ('Create a minimal working Databricks example with cluster and notebook') and when ('Use when starting a new Databricks project, testing your setup, or learning basic Databricks patterns') with explicit triggers.	3 / 3
Trigger Term Quality	It lists natural phrases users would say — 'databricks hello world', 'databricks example', 'databricks quick start', 'first databricks notebook', 'create cluster' — giving good coverage.	3 / 3
Distinctiveness Conflict Risk	The Databricks-scoped triggers ('databricks hello world', 'first databricks notebook') carve a clear niche unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 02d6341

Reviewed: about 7 hours 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.