CtrlK
BlogDocsLog inGet started
Tessl Logo

discover-tools

Discover available tools and resources in Databricks workspace. Use when: (1) User asks 'what tools are available', (2) Before writing agent code, (3) Looking for MCP servers, Genie spaces, UC functions, or vector search indexes, (4) User says 'discover', 'find resources', or 'what can I connect to'.

80

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

A well-structured, lean skill body that delivers an executable command with concrete options, a compact reference table, and clearly sequenced next steps pointing to sibling skills. It matches the rubric's good examples of brief, copy-paste-ready guidance without concept padding.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: it never explains what Databricks, MCP, Genie, or UC functions are, and every line (commands, options, the resource table) earns its place. It is not a 2 because there is no unnecessary explanation or padding to tighten.

3 / 3

Actionability

It provides the fully executable command 'uv run discover-tools' plus concrete, copy-paste-ready flag variations (--catalog, --schema, --format json, --output, --profile) and concrete MCP URL patterns. It is not a 2 because the guidance is complete and executable rather than pseudocode or missing key details.

3 / 3

Workflow Clarity

This is a simple single-task skill (under 50 lines) whose single action is unambiguous, with a clearly sequenced Next Steps list; the destructive-operation feedback-loop cap does not apply since discovery is read-only. It is not a 2 because the single action is unambiguous and follow-on steps are explicitly ordered.

3 / 3

Progressive Disclosure

No bundle files exist in references/scripts/assets, and the skill is under 50 lines with well-organized sections (Run Discovery, What Gets Discovered, Next Steps) and no need for external references. It is not a 2 because organization is clear and there is no inline content that should be split out.

3 / 3

Total

12

/

12

Passed

Description

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.

A strong description that uses third-person voice, states a concrete capability scoped to Databricks, and provides an explicit, enumerated 'Use when' clause with natural trigger terms. It clearly answers both what the skill does and when to invoke it.

DimensionReasoningScore

Specificity

It states a concrete action ('Discover available tools and resources') and enumerates multiple specific resource types ('MCP servers, Genie spaces, UC functions, or vector search indexes'), which is concrete and comprehensive rather than vague. It is not a 2 because the 2-anchor is 'not comprehensive', and this lists four specific discoverable resource categories.

3 / 3

Completeness

It explicitly answers both what ('Discover available tools and resources in Databricks workspace') and when via an explicit 'Use when: (1)...(2)...(3)...(4)...' clause. It is not a 2 because the when-guidance is explicit and enumerated, not merely implied.

3 / 3

Trigger Term Quality

It includes natural phrasings a user would actually say: "what tools are available", "discover", "find resources", and "what can I connect to". It is not a 2 because the 2-anchor misses common variations, whereas these cover several natural ways a user would request discovery.

3 / 3

Distinctiveness Conflict Risk

It is scoped to a clear Databricks-workspace niche with distinct triggers (e.g. 'what can I connect to', 'find resources') unlikely to fire for unrelated skills. It is not a 2 because the 2-anchor could still overlap with similar skills, while this Databricks/MCP/Genie/UC scope is distinctive.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
databricks/app-templates
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.