databricks-install-auth

Install and configure Databricks CLI and SDK authentication. Use when setting up a new Databricks integration, configuring tokens, or initializing Databricks in your project. Trigger with phrases like "install databricks", "setup databricks", "databricks auth", "configure databricks token", "databricks CLI".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

Quality

Content

77%

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

A highly actionable, well-sequenced install/auth skill with executable code and built-in verification plus an error-recovery table. Its main weaknesses are mild scope creep in the Examples section and a fully monolithic structure with no progressive disclosure into bundle files.

Suggestions

Move the Examples section (Account-Level Client, Azure AD Managed Identity) into a references/ file and link to it from the main flow, keeping SKILL.md focused on the core install/auth steps — this improves both conciseness and progressive_disclosure.

Add an explicit validation gate in Step 2 (e.g., "Only proceed to Step 3 once `databricks current-user me` succeeds") so the verify steps function as feedback loops rather than standalone checks.

Tighten the per-option prose (e.g., "Opens browser for OAuth consent. Token auto-refreshes (1-hour lifetime).") to one-line hints or move detail into the Error Handling/Resources sections.

Dimension	Reasoning	Score
Conciseness	The core install/auth flow is lean and assumes competence (no "what is Databricks" padding, deprecation correctly isolated in a WARNING block), but the Examples section (Account-Level Client, Azure AD Managed Identity) extends beyond the stated install/auth scope and could be tightened or relocated.	2 / 3
Actionability	Fully executable, copy-paste-ready guidance throughout: real install commands, env-var exports, a ~/.databrickscfg INI block, and complete Python SDK snippets with verification calls.	3 / 3
Workflow Clarity	A clearly sequenced Step 1–5 process with explicit verification checkpoints ("databricks --version", "databricks current-user me", the SDK smoke test) plus an Error Handling table that maps cause→solution for recovery.	3 / 3
Progressive Disclosure	Well-organized into labeled sections with easy navigation, but everything lives in one ~160-line inline file with no bundle references (references/, scripts/, assets/ are absent) and content such as Examples/Error Handling that could be split remains inline.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 states concrete capabilities and pairs them with an explicit "Use when" clause and a list of natural trigger phrases. It cleanly answers both what the skill does and when to activate it with minimal risk of conflicting with sibling skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Install and configure Databricks CLI and SDK authentication" — naming both the CLI and SDK plus the authentication task rather than vague language.	3 / 3
Completeness	Clearly answers both what (install/configure CLI and SDK auth) and when ("Use when setting up a new Databricks integration, configuring tokens, or initializing Databricks in your project") with explicit triggers.	3 / 3
Trigger Term Quality	Explicitly enumerates natural phrases users would say: "install databricks", "setup databricks", "databricks auth", "configure databricks token", "databricks CLI" — good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Databricks-specific niche with distinct triggers unlikely to collide with other skills; the named tooling (Databricks CLI/SDK) scopes it tightly.	3 / 3
	Total	12 / 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: 2 days 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.