Manage Databricks workspace connections: check current workspace, switch profiles, list available workspaces, or authenticate to a new workspace. Use when the user mentions "switch workspace", "which workspace", "current profile", "databrickscfg", "connect to workspace", or "databricks auth".
80
100%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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.
This is an excellent skill description that clearly defines its scope (Databricks workspace connection management), lists specific concrete actions, and provides explicit trigger terms in a 'Use when...' clause. It follows best practices with third-person voice, concise language, and distinct terminology that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: check current workspace, switch profiles, list available workspaces, and authenticate to a new workspace. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (manage Databricks workspace connections with four specific actions) and 'when' (explicit 'Use when...' clause with six specific trigger phrases). | 3 / 3 |
Trigger Term Quality | Includes excellent natural trigger terms that users would actually say: 'switch workspace', 'which workspace', 'current profile', 'databrickscfg', 'connect to workspace', 'databricks auth'. These cover multiple natural phrasings and variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche around Databricks workspace management. The specific trigger terms like 'databrickscfg', 'databricks auth', and 'switch workspace' are unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted, concise skill that maps user intents to specific MCP tool actions with clear parameters. The workflow is logically sequenced with appropriate detail for each action type. The constraint at the top (don't edit config files or use CLI) is a valuable safety boundary.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line serves a purpose. No unnecessary explanations of what Databricks is or how MCP tools work. The note at the end is justified as it clarifies session-scoping behavior that Claude wouldn't inherently know. | 3 / 3 |
Actionability | Provides specific tool names, exact parameter mappings (action/profile/host), a concrete intent-to-action mapping table, and clear output formatting instructions. The guidance is directly executable without ambiguity. | 3 / 3 |
Workflow Clarity | Clear 4-step sequence covering tool loading, intent mapping, execution, and result presentation. The switch action includes a prerequisite step (call list first), which is a useful validation checkpoint. For this non-destructive operation set, the workflow is appropriately detailed. | 3 / 3 |
Progressive Disclosure | This is a simple, single-purpose skill under 50 lines with no need for external references. The content is well-organized with a clear constraint statement, numbered steps, and a contextual note. No bundle files are needed. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
93cb4e3
Table of Contents
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.