What problem does it solve?
It resolves confusion around dbt State, the server-backed reuse mechanism that skips, clones, or rebuilds dbt nodes, and explains why models rebuild unexpectedly or fail to reuse existing objects.
Core Features & Use Cases
- Reuse decision guidance: Explains how dbt State chooses between skip, clone, and build for each selected node based on semantic hashes and data freshness.
- Configuration reference: Documents configs like lag_tolerance, evaluate_volatile_sql, pre_clone, and execute_hooks_on_any_reuse for tuning reuse behavior.
- Troubleshooting: Diagnoses unexpected rebuilds caused by volatile SQL, non-deterministic Jinja, or build-relevant config changes, and clarifies DATT-based billing.
- Use Case: A developer notices a model with current_timestamp() rebuilding every run; use this Skill to determine whether evaluate_volatile_sql or a Jinja-rendered value is invalidating the semantic hash.
Quick Start
Ask the agent why my dbt model keeps rebuilding despite no code changes and how to configure lag_tolerance for my dev environment.