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 actually 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 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 very unlikely to conflict with other skills.

Every section is lean and purposeful. No unnecessary explanations of what UC functions or vector search indexes are—assumes Claude knows. The table format is an efficient way to convey resource types and URL patterns.

Provides concrete, copy-paste-ready CLI commands with clear option flags. The table gives specific MCP URL patterns. Next steps point to specific skills for follow-up actions.

This is a single-task discovery skill with a clear primary action (run discover-tools) followed by well-sequenced next steps. Since discovery is a non-destructive read operation, validation checkpoints are not needed, and the workflow is unambiguous.

Content is 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.