CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

using-dbt-state

Use when a user is enabling, configuring, optimizing, or debugging dbt State (the server-backed reuse mechanism that clones or skips nodes instead of rebuilding them). Use when they conflate dbt State with the `state:modified` selector or `--state` deferral. Use when asked about models rebuilding unexpectedly, views with `select *` rebuilding, volatile SQL (`current_timestamp()`, `random()`) rebuilding or not, cross-developer cloning, lag_tolerance.

Quality

87%

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

75%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 strong, information-dense reference body that relies on tables for scannability and stays almost entirely on dbt-specific knowledge Claude would not already have. Main improvement levers are removing the triple-repeated install/version detail and splitting the billing and version-compatibility sections into reference files.

Suggestions

Consolidate the version/install information (currently repeated in the Common Misconceptions table, the v1 vs v2 table, and the bullets beneath it) into the single "v1 (Python) vs v2 (Rust/Fusion)" section and reference it elsewhere.

Move the DATT billing details and the version-compatibility matrix into a reference file (e.g. references/billing.md) and keep a one-line summary with a clearly signaled link in SKILL.md.

Add an explicit verification step in the diagnostics section (e.g. "confirm the fix by running `dbt-state explain <node>` and checking the decision changes") to close the feedback loop.

DimensionReasoningScore

Conciseness

Dense with dbt-specific facts Claude would not know (semantic-hash comparison, DATT billing, volatile-SQL handling) and free of generic tutoring, but the pip-install guidance for dbt Core 1.7–1.11 is repeated in three places (misconceptions table, version table, and bullet list) and the misconception table restates the `state:modified` distinction already made in the intro.

4 / 5

Actionability

Concrete and executable in most places: a configs table with defaults and valid values, a copy-paste YAML example for per-environment lag_tolerance, specific commands (`pip install dbt-state`, `dbt-state explain`), and a symptom-to-fix diagnostic table. Minor gaps: no example of the `state-org-id` or `schema.yml` config syntax.

4 / 5

Workflow Clarity

As an explanation/reference skill it is well-sequenced (misconceptions → decision logic → why models rebuild → configs → billing → optimizations → diagnosis table that acts as a decision flow), and the "Diagnosing confusing behavior" table gives explicit symptom-to-cause-to-fix mappings. It loses a point because there is no explicit validation/check step for, e.g., verifying a config change took effect via `dbt-state explain` before and after.

4 / 5

Progressive Disclosure

The single file is well-organized with clear section headers and no nested or dead references (no bundle files exist, and the "Related docs" links are clearly-signaled one-level pointers). However, at ~110 lines, content that could live in separate references (billing/DATT detail, the v1-vs-v2 version matrix) is inlined in the main file.

4 / 5

Total

16

/

20

Passed

Description

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

An excellent description: it explicitly states what the skill covers, gives multiple concrete natural-language trigger phrases, and proactively disambiguates from the most confusable adjacent feature. Only minor room to sharpen the action verbs beyond the generic enabling/configuring/optimizing/debugging list.

DimensionReasoningScore

Specificity

Concrete scope is stated ("the server-backed reuse mechanism that clones or skips nodes instead of rebuilding them") with named actions (enabling, configuring, optimizing, debugging), but the verbs themselves are generic and coverage of specific actions is minor-gapped rather than comprehensive.

4 / 5

Completeness

Explicitly answers both: what ("the server-backed reuse mechanism that clones or skips nodes instead of rebuilding them") and when (three explicit "Use when..." clauses with concrete trigger phrases).

5 / 5

Trigger Term Quality

Natural phrases a user would actually say are comprehensively covered: "models rebuilding unexpectedly", "views with select * rebuilding", "volatile SQL (current_timestamp(), random())", "cross-developer cloning", "lag_tolerance", plus the exact identifiers `state:modified` and `--state`.

5 / 5

Distinctiveness Conflict Risk

Clear niche (dbt State specifically) with distinct triggers; it even pre-empts the nearest conflict by explicitly distinguishing dbt State from the `state:modified` selector and `--state` deferral.

5 / 5

Total

19

/

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/using-dbt-state/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.