CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

querying-the-dbt-information-schema

Use when answering questions about a dbt v2 project's own metadata — which models, sources, tests, columns, configs, tags, packages or lineage exist, what is untested or undocumented, what depends on what, how long models took in the last run — or when using `dbt show --info`, `{{ info_schema() }}`, `--generate-info-schema`, `target/info_schema/`, or writing `dbt check` SQL. Prefer this over grepping YAML or parsing `manifest.json` on dbt v2.

Quality

90%

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

92%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.

An exemplary skill body: fully executable commands and queries, a clearly sequenced route-selection workflow with explicit error-recovery loops, and a clean split between inline operational guidance and the one offloaded column reference. The only flaw is minor redundancy between the route comparison table and the Route B difference bullets.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious, dbt-specific facts (misrouting symptoms, double-encoded config, 'null' string quirk, stale target/ dirs) and teaches nothing Claude already knows, so it mostly assumes competence. Minor trimming is possible — the Route A/B comparison table and the Route B 'How this differs' bullets repeat each other, and the Contents table re-lists the section headers — which keeps it below the every-token-earns-its-place anchor.

4 / 5

Actionability

Everything is copy-paste executable: complete 'dbt show' commands with the right flags, six ready-to-run SQL queries (untested models, missing descriptions, recursive lineage, materializations, incremental strategies, slowest models), a check file plus dbt_project.yml and checks YAML, and even the describe query to discover columns. Specific error codes ('InfoSchemaUnavailable (dbt1656)', 'unknown function: Jinja macro or function ref is unknown') make failure diagnosis concrete.

5 / 5

Workflow Clarity

The routing workflow is clearly sequenced (verify dbt v2 → confirm metadata exists via the invocations query → pick Route A/B via the trade-off table) with explicit validation and feedback loops: 'If you get 0 rows from a view that should have data, refresh the metadata with dbt parse --generate-info-schema and retry'; misrouted queries are diagnosed by symptom ('A slow query or a warehouse error means the query went to the wrong engine'); Route B staleness is checked by comparing file mtime against the invocations row; and the check-conversion workflow includes testing with 'dbt check <name> --select <resources>' and cautionary gating before creating files.

5 / 5

Progressive Disclosure

The bulky column reference is correctly split into references/view-columns.md (a real file, one level deep, clearly signaled in the Reference section with a descriptive label), while the operational guidance (gotchas, common queries, checks) stays inline where it is needed at query time. A Contents routing table at the top plus a route-decision table makes navigation easy, and links are one level deep with no nesting.

5 / 5

Total

19

/

20

Passed

Description

86%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, trigger-rich description with explicit 'Use when' guidance, comprehensive natural and technical keywords, and explicit disambiguation from alternative approaches. The only gap is that the capability itself (querying the metadata views with DuckDB SQL) is implied by the question list rather than stated directly.

DimensionReasoningScore

Specificity

Enumerates many concrete capability areas — 'which models, sources, tests, columns, configs, tags, packages or lineage exist, what is untested or undocumented, what depends on what, how long models took in the last run' — plus specific tooling entry points. It stops short of anchor 5 because the actual action (querying the information-schema views with SQL) is never stated as a verb, only implied by the question list and tool flags.

4 / 5

Completeness

The 'when' is explicit and rich ('Use when answering questions about a dbt v2 project's own metadata — … — or when using …'), and the 'what' is present via the enumerated question types, but the what-side is outcome phrasing rather than the skill's mechanism. It fits anchor 4 (both present, one side could be more explicit) rather than anchor 5, which expects the capability itself stated as concretely as the triggers.

4 / 5

Trigger Term Quality

Comprehensive natural-language and technical triggers: 'what depends on what', 'untested or undocumented', 'how long models took in the last run', plus exact strings a user or transcript would contain — 'dbt show --info', '{{ info_schema() }}', '--generate-info-schema', 'target/info_schema/', 'dbt check' SQL, 'manifest.json', 'grepping YAML'. Matches the anchor-5 pattern of covering synonyms, commands, and file paths.

5 / 5

Distinctiveness Conflict Risk

Clear niche (dbt v2 project metadata) with distinct triggers, and it actively disambiguates against the nearest competing approaches: 'Prefer this over grepping YAML or parsing manifest.json on dbt v2.' Minimal conflict risk with generic dbt, SQL, or documentation skills.

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/querying-the-dbt-information-schema/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.