Lists multiple specific concrete actions and resources: discovering MCP servers, Genie spaces, UC functions, and vector search indexes within a Databricks workspace. These are concrete, identifiable resource types.

Clearly answers both 'what' (discover available tools and resources in Databricks workspace) and 'when' with an explicit numbered list of trigger scenarios including user phrases and contextual triggers like 'before writing agent code'.

Includes strong natural trigger terms users would say: 'what tools are available', 'discover', 'find resources', 'what can I connect to', plus specific technical terms like 'MCP servers', 'Genie spaces', 'UC functions', 'vector search indexes' that users in the Databricks ecosystem would naturally use.

Highly distinctive with a clear niche: Databricks workspace resource discovery. The specific resource types (MCP servers, Genie spaces, UC functions, vector search indexes) and the discovery/exploration focus make it unlikely to conflict with other skills.

Every token earns its place. No unnecessary explanations of what UC functions or vector search indexes are—assumes Claude knows these concepts. The table format is efficient for conveying resource type mappings.

Provides concrete, copy-paste ready commands with clear options and flags. The MCP URL patterns in the table give specific, actionable information for constructing endpoints. Next steps point to specific skills for follow-up actions.

This is a single-task skill (run discovery), and the single action is unambiguous. The workflow is clear: run discovery first, then follow next steps. The numbered next steps provide a logical sequence for what comes after discovery.

Well-structured with clear sections (Run Discovery → What Gets Discovered → Next Steps). References to other skills (modify-agent, add-tools, run-locally, create-tools) are one level deep and clearly signaled with bold skill names and descriptions of what each provides.