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.
89
86%
Does it follow best practices?
Impact
Pending
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, includes natural trigger terms, and explicitly defines when it should be used. It covers a well-defined niche within the Databricks agent configuration domain with minimal risk of conflicting with other skills. The use of third person voice and concise structure make it effective for skill selection.
| 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, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (add tools and grant permissions in databricks.yml) and 'when' with an explicit 'Use when:' clause listing four distinct trigger scenarios including user phrases and situational triggers. | 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 user-facing phrases and technical terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific Databricks ecosystem terms (databricks.yml, MCP servers, Genie spaces, vector search, UC functions). Unlikely to conflict with other skills due to the narrow, well-defined domain. | 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 that provides actionable, concrete guidance for adding tools and granting permissions in Databricks agents. Its main strengths are the executable code examples, clear resource type reference table, and good progressive disclosure to example files. The main weaknesses are minor verbosity in explanatory sections and the lack of validation/verification steps after deploying permission changes.
Suggestions
Add a validation step after deployment (e.g., 'Step 4: Verify permissions by checking app status with `databricks apps get <app-name> --profile <profile>` or testing the tool call')
Trim the MCP Error Handling section to just the timeout customization code and a one-line note about default error handling, removing the explanation of SDK behavior Claude can infer
| 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 'Important Notes' section contains some obvious reminders that could be trimmed. | 2 / 3 |
Actionability | Provides fully executable Python code for adding MCP servers, complete YAML snippets for granting permissions, and specific commands for deployment. The examples are copy-paste ready with realistic resource IDs and structure. | 3 / 3 |
Workflow Clarity | The 3-step workflow is clearly sequenced (add server → grant access → deploy), but lacks explicit validation checkpoints. There's no step to verify permissions were granted correctly or to check for errors after deployment, which is important for permission-granting operations that can fail silently. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview workflow, a well-organized reference table pointing to example files in `examples/` directory, and clear cross-references to related skills (create-tools, deploy). References are one level deep and clearly signaled. | 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.
dfeb4ac
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.