create-tools
Create Databricks resources that agents connect to as tools. Use when: (1) User needs to create a Genie space, vector search index, UC function, or UC connection, (2) User says 'create tool', 'set up genie', 'create vector search', 'register MCP server', (3) Before add-tools when the resource doesn't exist yet, (4) User asks 'what do I need to create before adding this tool'.
86
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 defines its scope (creating Databricks resources), lists specific resource types, provides natural trigger phrases, and explicitly differentiates itself from a related 'add-tools' skill. The 'Use when' clause is comprehensive with four distinct scenarios covering different user intents. The description is concise yet thorough, using proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: create Genie space, vector search index, UC function, UC connection, and register MCP server. These are clearly defined, concrete resources rather than vague abstractions. | 3 / 3 |
Completeness | Clearly answers both 'what' (create Databricks resources that agents connect to as tools) and 'when' with an explicit 'Use when:' clause containing four distinct trigger scenarios, including relationship to other skills ('Before add-tools when the resource doesn't exist yet'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'create tool', 'set up genie', 'create vector search', 'register MCP server', plus domain-specific terms like 'Genie space', 'vector search index', 'UC function', 'UC connection'. Good coverage of natural trigger phrases. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Databricks-specific terminology (Genie space, UC function, UC connection, vector search index) and clear differentiation from a related 'add-tools' skill. The niche is well-defined and unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 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 well-structured routing/overview skill that efficiently directs users to the right resource creation guide. Its main weakness is that it contains almost no actionable content itself—all concrete guidance is delegated to example files that aren't provided in the bundle. Adding a validation step after resource creation and ensuring the referenced files exist would strengthen it significantly.
Suggestions
Add a brief validation step after resource creation in the workflow (e.g., 'Verify: confirm the resource appears in `uv run discover-tools` output before proceeding')
Include at least one minimal concrete example inline (e.g., a quick UC function creation snippet) so the skill has some standalone actionability
Provide the referenced bundle files (examples/genie-space.md, etc.) or note their expected locations so progressive disclosure can be fully evaluated
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line serves a purpose. The table is an efficient decision matrix, the workflow is minimal, and there's no explanation of concepts Claude already knows. The introductory blockquote is brief and contextually useful. | 3 / 3 |
Actionability | The skill provides a clear decision table and references to detailed guides, but contains no executable code or concrete commands beyond `uv run discover-tools`. The actual creation steps are entirely delegated to example files which are not provided in the bundle. | 2 / 3 |
Workflow Clarity | The 4-step workflow is clearly sequenced and logically ordered, but lacks validation checkpoints. There's no verification step after resource creation (e.g., confirming the resource exists before proceeding to add-tools), which is important for operations that create infrastructure resources. | 2 / 3 |
Progressive Disclosure | The structure is well-organized with a clear overview and one-level-deep references to five example files and three related skills. However, no bundle files were provided, so we cannot verify the referenced paths exist. The references themselves are clearly signaled via the table format, but the skill is entirely dependent on those external files for any substantive content. | 2 / 3 |
Total | 9 / 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.
- Repository
- databricks/app-templates
- Commit
dfeb4ac
- 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.