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

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

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

SKILL.md
Quality
Evals
Security

Quality

Content

93%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.

A concise, actionable, well-organized skill body that gives executable commands and clear next-step navigation without over-explaining. The only minor gap is guidance on interpreting and acting on discovery output.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: a single command, a compact options block, and a resource table with no padding or explanation of concepts Claude already knows.

5 / 5

Actionability

Provides copy-paste-ready, executable commands ("uv run discover-tools") with concrete flags (--catalog, --schema, --format json, --output, --profile) covering the common cases.

5 / 5

Workflow Clarity

The single discovery action is unambiguous and the Next Steps are numbered, but guidance on how to select or use discovered resources is left to sibling skills, leaving a minor gap.

4 / 5

Progressive Disclosure

Under 50 lines with well-organized sections (Run Discovery, What Gets Discovered, Next Steps) and one-level-deep, clearly signaled references to sibling skills, satisfying the simple-skill exception.

5 / 5

Total

19

/

20

Passed

Description

91%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.

A strong, well-structured description that clearly conveys both purpose and trigger conditions with concrete Databricks-specific examples. Minor room for improvement on distinctiveness given the somewhat generic discovery verbs.

DimensionReasoningScore

Specificity

Names the Databricks domain and enumerates several concrete resource types ("MCP servers, Genie spaces, UC functions, or vector search indexes"), but the single verb "Discover" keeps it just shy of comprehensive multi-action coverage.

4 / 5

Completeness

Explicitly states what it does ("Discover available tools and resources in Databricks workspace") and provides a numbered "Use when" clause with concrete trigger phrases, answering both what and when.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ("what tools are available", "discover", "find resources", "what can I connect to") with synonyms, giving comprehensive coverage of likely triggers.

5 / 5

Distinctiveness Conflict Risk

The Databricks-specific niche and enumerated resource types make it largely distinct, but generic verbs like "discover" and "find resources" carry minor overlap risk with adjacent skills.

4 / 5

Total

18

/

20

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.