CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fetching-dbt-docs

Retrieves and searches dbt documentation pages in LLM-friendly markdown format. Use when fetching dbt documentation, looking up dbt features, or answering questions about dbt Cloud, dbt Core, or the dbt Semantic Layer.

Quality

85%

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 dbt-labs/dbt-agent-skills

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 well-structured, efficient skill body: URL patterns and resources are in compact tables, the two-step search workflow has an explicit escalation condition, and the search implementation is correctly externalized to a real bundle script with clear usage. The only weaknesses are minor: the `.md` rule is stated three times, and a couple of placeholders/shorthand invocations are not literally copy-paste ready.

Suggestions

State the `.md` suffix rule once (e.g., in the URL Pattern section) and drop the repetition in 'Fetching a Single Page' and the Common Mistakes table to tighten conciseness.

Add a brief fallback for the case where both the llms.txt index and the full-docs search return no results (e.g., try broader/synonym keywords or check the reference section of the docs) to strengthen the workflow's validation loop.

Consider making the WebFetch examples literal enough to execute verbatim (e.g., noting the exact URL plus the `.md` suffix in one line) so guidance is fully copy-paste ready.

DimensionReasoningScore

Conciseness

The body is lean and table-driven with no padding or explanation of concepts Claude already knows, matching the 4 anchor ('efficient; minor instances of over-explanation that could be trimmed'). The '.md' suffix instruction is repeated three times ("Always append `.md`" in Overview, "Always add `.md` to the URL path", and the Common Mistakes table row), which keeps it below the 5 anchor.

4 / 5

Actionability

Concrete URLs, a WebFetch invocation pattern with an example prompt, and copy-paste-ready script commands with realistic examples ("semantic_model", "'incremental strategy'", "--fresh") make this mostly executable per the 4 anchor. The `<SKILL_BASE_DIR>` placeholder and the shorthand `WebFetch:` blocks (not literal tool calls) are minor gaps against fully copy-paste-ready 5, though the placeholder substitution is explicitly justified.

4 / 5

Workflow Clarity

The page-finding workflow is clearly sequenced — "Step 1: Search the Index First" ("This is fast and usually sufficient") then "Step 2: Search Full Docs (Only if Needed)" with the explicit condition "If the index doesn't have results", followed by fetching pages. No validation steps are needed since the operations are read-only. It stops short of 5 because there is no checkpoint for the zero-results-in-both case and escalation relies on a single implicit conditional rather than an explicit feedback loop.

4 / 5

Progressive Disclosure

The SKILL.md is a concise overview (~80 lines) and the heavy machinery — the full-docs search implementation — is properly delegated to `scripts/search-dbt-docs.sh`, which exists in the bundle and is referenced by exact relative path with usage, examples, and cache notes. The reference is one level deep and clearly signaled, matching the 5 anchor; not 4 because nothing that belongs in a separate file is inlined and navigation is unambiguous.

5 / 5

Total

17

/

20

Passed

Description

87%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 description: concrete actions, explicit output format, third-person voice, and a well-formed 'Use when...' clause with multiple concrete trigger phrases. Minor room to broaden natural synonyms (e.g., 'dbt docs', 'dbt commands').

DimensionReasoningScore

Specificity

Names the domain and two concrete actions — "Retrieves and searches dbt documentation pages in LLM-friendly markdown format" — with the output format made explicit. It falls short of the 5 anchor because only two capabilities are listed rather than multiple specific actions with comprehensive coverage.

4 / 5

Completeness

Explicitly answers both: what ("Retrieves and searches dbt documentation pages in LLM-friendly markdown format") and when ("Use when fetching dbt documentation, looking up dbt features, or answering questions about dbt Cloud, dbt Core, or the dbt Semantic Layer") with concrete trigger phrases, matching the 5 anchor's structure. Not below 4 because the 'when' clause is neither vague nor implicit.

5 / 5

Trigger Term Quality

Natural phrases like "fetching dbt documentation", "looking up dbt features", and product names "dbt Cloud, dbt Core, or the dbt Semantic Layer" give good keyword coverage. A few natural variations users would say (e.g., "dbt docs", "dbt commands", "dbt configuration") are missing, so it sits between the 4 and 5 anchors, clearly above the 3 anchor's missing-synonyms profile.

4 / 5

Distinctiveness Conflict Risk

The dbt-specific niche (docs.getdbt.com content, dbt Cloud/Core/Semantic Layer) is clearly distinct with trigger terms unlikely to fire for unrelated skills. This matches the 5 anchor's 'clear niche with distinct triggers; minimal conflict risk'.

5 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

dbt-labs/dbt-agent-skills

Path

skills/dbt/skills/fetching-dbt-docs/SKILL.md

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.