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".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/databricks-pack/skills/databricks-install-auth/SKILL.mdQuality
Discovery
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 well-structured skill description that clearly communicates its purpose and includes explicit trigger guidance. Its main weakness is that the capability listing could be more granular—specifying concrete actions beyond 'install and configure'. Overall, it performs well across completeness, trigger terms, and distinctiveness.
Suggestions
Add more specific concrete actions such as 'generate authentication tokens', 'configure .databrickscfg profiles', 'validate CLI connection' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Databricks CLI/SDK authentication) and some actions (install, configure, authentication), but doesn't list multiple concrete actions in detail—e.g., it doesn't specify steps like 'generate tokens', 'validate connection', 'set up profiles', etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (install and configure Databricks CLI and SDK authentication) and 'when' (setting up new integration, configuring tokens, initializing Databricks) with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'install databricks', 'setup databricks', 'databricks auth', 'configure databricks token', 'databricks CLI'. These cover common variations well. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Databricks CLI/SDK authentication setup, which is a clear niche. The trigger terms are distinct and unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with executable code examples covering multiple authentication methods. Its main weaknesses are length (advanced examples and the error table could be externalized) and the lack of integrated validation/feedback loops in the workflow steps. The content is well-organized but could be tightened by moving advanced scenarios to separate files and embedding verification checks directly into the step sequence.
Suggestions
Add explicit validation checkpoints within the workflow, e.g., 'If `databricks --version` fails, ensure the install script completed and the binary is on PATH before proceeding'
Move advanced examples (Account-Level Client, Azure AD Managed Identity) and the error handling table to a separate REFERENCE.md or TROUBLESHOOTING.md file, linked from the main skill
Remove explanatory phrases Claude already knows (e.g., 'Uses client credentials flow. No browser required.', 'Opens browser for OAuth consent.') to improve conciseness
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary commentary (e.g., 'Databricks strongly recommends OAuth over PATs for production', explanations of what OAuth U2M/M2M are). The error handling table and multiple auth examples add bulk, though most is useful reference material. | 2 / 3 |
Actionability | Provides fully executable bash commands, Python code, and config file examples that are copy-paste ready. Each authentication method has concrete, runnable examples with realistic placeholder values and verification commands. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but there are no explicit validation checkpoints or feedback loops between steps. Step 4 verifies the connection but there's no 'if this fails, go back to step X' guidance. The error handling table is separate rather than integrated into the workflow. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and sections, and links to external docs are provided. However, the file is quite long (~150 lines of content) with advanced examples (Account-Level Client, Azure AD Managed Identity) that could be split into separate reference files rather than inlined. | 2 / 3 |
Total | 9 / 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.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
70e9fa4
- 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.