fetching-dbt-docs
Use when fetching dbt documentation, looking up dbt features, or answering questions about dbt Cloud, dbt Core, or the dbt Semantic Layer
Install with Tessl CLI
npx tessl i github:dbt-labs/dbt-agent-skills --skill fetching-dbt-docs86
Quality
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Discovery
62%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 excels at trigger terms and distinctiveness by clearly targeting the dbt ecosystem with specific product names. However, it fails to describe what the skill actually does beyond vague 'fetching' and 'answering questions', and inverts the typical structure by only providing 'when' guidance without explaining capabilities.
Suggestions
Add specific capabilities before the 'Use when' clause, e.g., 'Retrieves dbt best practices, configuration syntax, model definitions, and troubleshooting guidance.'
Replace vague actions like 'fetching documentation' and 'answering questions' with concrete actions like 'explains Jinja macros, resolves dependency errors, provides YAML configuration examples'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'fetching documentation', 'looking up features', and 'answering questions' without specifying concrete actions. It doesn't describe what the skill actually does beyond generic information retrieval. | 1 / 3 |
Completeness | The description focuses entirely on 'when' (Use when...) but lacks a clear 'what does this do' component. It tells Claude when to use it but not what capabilities or actions the skill provides. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'dbt documentation', 'dbt features', 'dbt Cloud', 'dbt Core', 'dbt Semantic Layer'. These are specific product names and terms users would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | The description is highly specific to dbt ecosystem (dbt Cloud, dbt Core, dbt Semantic Layer) and unlikely to conflict with other skills. The niche is clearly defined around dbt-related queries. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that demonstrates best practices: it's concise, provides executable examples, has a clear workflow with explicit ordering (index first, full docs second), and includes a helpful 'Common Mistakes' section that serves as implicit validation guidance. The content respects Claude's intelligence while providing the specific, non-obvious information needed to interact with dbt docs effectively.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only essential information without explaining what dbt is or how web fetching works. Every section serves a clear purpose with no padding. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready commands and URLs. The bash script examples with actual arguments and the WebFetch commands are immediately executable. | 3 / 3 |
Workflow Clarity | Clear two-step workflow (search index first, then full docs only if needed) with explicit sequencing. The 'Common Mistakes' table serves as validation guidance to prevent errors. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from overview to quick reference to detailed usage. References external script appropriately without nesting. Content is appropriately sized for a single file. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.