Name: create-tools
Rating: 64.8 (1 reviews)
Author: databricks

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'.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./agent-non-conversational/.claude/skills/create-tools/SKILL.md

The canonical home for this skill is create-tools in databricks/app-templates

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is admirably concise and well-structured as an overview, but it over-delegates: the actual creation instructions live in example files that are missing from the bundle, and the workflow lacks validation checkpoints for a resource-creation task.

Suggestions

Provide the referenced example files (examples/genie-space.md, examples/vector-search-index.md, examples/uc-function.md, examples/uc-connection.md, examples/local-python-tools.md) or inline a minimal executable snippet for each resource type so the core 'Create' step is actionable.

Add an explicit validation checkpoint after creation, e.g., 'Verify the resource exists with discover-tools before proceeding to add-tools', and a check that the resource does not already exist before creating it.

If the example files are intentionally external, confirm they ship in the bundle; otherwise replace the dangling references with inline guidance to avoid dead links.

Dimension	Reasoning	Score
Conciseness	The body is lean (under 30 lines), assumes Claude's competence, and never explains what Databricks/Genie/UC functions are — every token earns its place.	5 / 5
Actionability	The decision table maps intents to resources and one concrete command is present ('uv run discover-tools'), but the core 'Create' step has no inline executable guidance — it delegates to example guide files that do not exist in the bundle, leaving key execution details missing.	3 / 5
Workflow Clarity	A clear four-step sequence (Discover → Create → Add → Deploy) is present, but there are no validation checkpoints (e.g., verify the resource was created or confirm it does not already exist before creating), capping a resource-creation workflow at 3.	3 / 5
Progressive Disclosure	The overview structure and one-level-deep reference signaling are good, but every referenced guide file (examples/genie-space.md, examples/vector-search-index.md, etc.) is absent from the bundle, so navigation leads to dead ends.	3 / 5
	Total	14 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it states the capability concretely, provides an explicit multi-clause 'Use when' trigger list, and draws a clear boundary against the sibling add-tools skill. Its only weak spot is reliance on a single action verb and somewhat limited trigger synonyms.

Dimension	Reasoning	Score
Specificity	Names the Databricks domain and enumerates concrete resource types ('Genie space, vector search index, UC function, or UC connection'), but the action verb is essentially a single one ('Create') rather than multiple distinct actions, leaving a minor coverage gap.	4 / 5
Completeness	Explicitly answers both what ('Create Databricks resources that agents connect to as tools') and when, with a concrete four-clause 'Use when' trigger list — a direct match to the top anchor.	5 / 5
Trigger Term Quality	Includes several natural user utterances ('create tool', 'set up genie', 'create vector search', 'register MCP server'), giving good keyword coverage, but lacks synonyms/variations for each resource type.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (creating Databricks tool resources) and explicitly disambiguates from the related 'add-tools' skill ('Before add-tools when the resource doesn't exist yet'), minimizing conflict risk.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: databricks/app-templates
Path: agent-non-conversational/.claude/skills/create-tools/SKILL.md
Commit: fdc1b49

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.