Add tools to your agent and grant required permissions in databricks.yml. Use when: (1) Adding MCP servers, Genie spaces, vector search, or UC functions to agent, (2) Permission errors at runtime, (3) User says 'add tool', 'connect to', 'grant permission', (4) Configuring databricks.yml resources.
71
86%
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 a strong skill description that clearly communicates specific capabilities (adding tools, granting permissions) within a well-defined domain (Databricks agent configuration). It includes explicit trigger conditions with both user-facing language and technical scenarios, making it easy for Claude to select appropriately from a large skill set.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: adding MCP servers, Genie spaces, vector search, UC functions, granting permissions, and configuring databricks.yml resources. These are concrete, identifiable tasks. | 3 / 3 |
Completeness | Clearly answers both 'what' (add tools to agent and grant permissions in databricks.yml) and 'when' with an explicit 'Use when:' clause listing four distinct trigger scenarios including user phrases and error conditions. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'add tool', 'connect to', 'grant permission', 'MCP servers', 'Genie spaces', 'vector search', 'UC functions', 'databricks.yml', 'permission errors'. Good coverage of both natural language and domain-specific terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific references to databricks.yml, MCP servers, Genie spaces, vector search, and UC functions. These are niche enough to avoid conflicts with general coding or configuration skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%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-structured skill with strong actionability and progressive disclosure. The main workflow is clear but would benefit from validation checkpoints after deployment. Some minor verbosity could be trimmed, particularly around explaining default SDK behavior and obvious notes.
Suggestions
Add a validation step after 'databricks bundle deploy' to verify permissions were granted correctly (e.g., checking app status or testing a tool call), which would improve workflow clarity.
Remove or condense the 'Important Notes' section — items like 'Deploy after changes' and 'Already configured in template' are either obvious or could be inline comments in the workflow steps.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but has some unnecessary explanation (e.g., 'Without this, you'll get permission errors when the agent tries to use the resource' and the MCP error handling section explaining SDK default behavior). The notes section also contains some obvious guidance like 'Deploy after changes'. | 2 / 3 |
Actionability | Provides fully executable Python code for adding MCP servers, complete YAML snippets for granting permissions, and a clear resource type reference table. The examples are copy-paste ready with realistic structure. | 3 / 3 |
Workflow Clarity | The 3-step workflow is clearly sequenced, but lacks validation checkpoints. There's no step to verify the deployment succeeded, no guidance on checking that permissions were actually granted, and no error recovery loop if the deploy fails or permissions are incorrect. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview, clear references to example files in the `examples/` directory via a well-organized table, and appropriate cross-references to related skills (create-tools, deploy). Content is well-split between inline essentials and external detailed examples. | 3 / 3 |
Total | 10 / 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.
3f07ee7
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.