databricks-docs
Databricks documentation reference via llms.txt index. Use when other skills do not cover a topic, looking up unfamiliar Databricks features, or needing authoritative docs on APIs, configurations, or platform capabilities.
73
66%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./databricks-skills/databricks-docs/SKILL.mdQuality
Discovery
75%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 well-structured with a clear 'what' and 'when' clause, and it effectively positions itself as a fallback documentation reference for Databricks topics. Its main weakness is that the capability description is somewhat general ('documentation reference') rather than listing specific concrete actions, and the trigger terms could include more specific Databricks feature names that users would naturally mention.
Suggestions
Add specific concrete actions like 'look up API reference details, retrieve configuration parameters, find syntax examples, and resolve platform feature questions' to improve specificity.
Include more natural Databricks-specific trigger terms users might say, such as 'Unity Catalog', 'Delta Lake', 'Databricks SQL', 'workspace', 'cluster configuration', or 'notebook' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Databricks documentation) and the general action (documentation reference via llms.txt index), but does not list multiple specific concrete actions like 'look up API endpoints, retrieve configuration guides, find platform feature docs'. | 2 / 3 |
Completeness | Clearly answers both 'what' (Databricks documentation reference via llms.txt index) and 'when' (when other skills don't cover a topic, looking up unfamiliar Databricks features, or needing authoritative docs on APIs/configurations/platform capabilities) with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Databricks', 'APIs', 'configurations', 'platform capabilities', and 'docs', but misses common user variations like 'Databricks SQL', 'Unity Catalog', 'Delta Lake', 'workspace settings', or specific feature names users might naturally mention. | 2 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche as a Databricks-specific documentation lookup skill, and the 'Use when other skills do not cover a topic' clause positions it as a fallback reference, making it unlikely to conflict with more specific Databricks skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a reasonably well-structured reference skill that clearly communicates its purpose and points to related resources. Its main weaknesses are moderate verbosity in explaining its own role and a lack of concrete, executable examples (e.g., an actual WebFetch call with the URL). The progressive disclosure and organization are strong points.
Suggestions
Add a concrete, executable example of fetching and searching llms.txt (e.g., show the actual WebFetch tool invocation with the URL rather than just describing it)
Trim the 'Role of This Skill' section — the distinction between reference and action skills can be conveyed in one sentence rather than a full section with bullet points
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'This is a reference skill, not an action skill' and the detailed 'Role of This Skill' section explaining what a reference is). The bullet lists describing when to use it are somewhat redundant. However, it's not egregiously verbose. | 2 / 3 |
Actionability | It provides a concrete URL and mentions using WebFetch, but lacks an executable example of the actual fetch command or how to parse/search the llms.txt content. The guidance is more directional than copy-paste ready. | 2 / 3 |
Workflow Clarity | The 'How to Use' section provides a 3-step sequence and the examples show multi-step workflows, but the steps are fairly vague ('Search for relevant sections/links') with no validation checkpoints or error handling guidance. For a reference skill this is adequate but not exemplary. | 2 / 3 |
Progressive Disclosure | The skill is well-organized with clear sections, provides a concise overview of the documentation structure, and links to related skills with one-level-deep references. The content is appropriately scoped for a reference/index skill. | 3 / 3 |
Total | 9 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- databricks-solutions/ai-dev-kit
- Commit
02aac8c
- 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.