npx skills add ...
npx skills add dbt-labs/dbt-agent-skills --skill running-dbt-commands
npx skills add dbt-labs/dbt-agent-skills --skill running-dbt-commands
Formats and executes dbt CLI commands, selects the correct dbt executable, and structures command parameters. Use when running models, tests, builds, compiles, or show queries via dbt CLI. Use when unsure which dbt executable to use or how to format command parameters.
dbt_build, dbt_run, dbt_show, etc.) - they handle paths, timeouts, and formatting automaticallybuild — even when users say "run" - When a user asks to "run" a model, recommend dbt build instead. build = run + test in one step, so it catches data quality issues immediately. dbt run alone is almost never the right answer during development.--quiet with --warn-error-options '{"error": ["NoNodesForSelectionCriteria"]}' to reduce output while catching selector typos--select - never run the entire project without explicit user approvalThree CLIs exist. Ask the user which one if unsure.
| Flavor | Location | Notes |
|---|---|---|
| dbt Core | Python venv | pip show dbt-core or uv pip show dbt-core |
| dbt Fusion | ~/.local/bin/dbt or dbtf | Faster and has stronger SQL comprehension |
| dbt Cloud CLI | ~/.local/bin/dbt | Go-based, runs on platform |
Common setup: Core in venv + Fusion at ~/.local/bin. Running dbt uses Core. Use dbtf or ~/.local/bin/dbt for Fusion.
Always provide a selector. Graph operators:
| Operator | Meaning | Example |
|---|---|---|
model+ | Model and all downstream | stg_orders+ |
+model | Model and all upstream | +dim_customers |
+model+ | Both directions | +orders+ |
model+N | Model and N levels downstream | stg_orders+1 |
Resource type filter:
Valid types: model, test, unit_test, snapshot, seed, source, exposure, metric, semantic_model, saved_query, analysis
Fusion:
--resource-typeis not supported withdbt test(dbt-fusion#1628). To run unit tests in Fusion:
dbt build --select model_name— builds the model first, then runs all tests including unit testsdbt build --select unit_test_name— targets a specific unit test by namedbt list --resource-type unit_test— lists unit test names for use in selectors
Use dbt list to preview what will be selected before running. Helpful for validating complex selectors.
Available output keys for --output json:
unique_id, name, resource_type, package_name, original_file_path, path, alias, description, columns, meta, tags, config, depends_on, patch_path, schema, database, relation_name, raw_code, compiled_code, language, docs, group, access, version, fqn, refs, sources, metrics
Preview data with dbt show. Use --inline for arbitrary SQL queries.
Important: Use --limit flag, not SQL LIMIT clause.
Pass as STRING, not dict. No special characters (\, \n).
After a dbt command, check target/run_results.json for detailed execution info:
Key fields:
status: success, error, fail, skipped, warnexecution_time: seconds spent executingcompiled_code: rendered SQLadapter_response: database metadata (rows affected, bytes processed)Reference production data instead of building upstream models:
Flags:
--defer - enable deferral to state manifest--state <path> - path to manifest from previous run (e.g., production artifacts)--favor-state - prefer node definitions from state even if they exist locallyOverride SQL analysis for models with dynamic SQL or unrecognized UDFs:
| Mistake | Fix |
|---|---|
Using test after model change | Use build - test doesn't refresh the model |
Running without --select | Always specify what to run |
Using --quiet without warn-error | Add --warn-error-options '{"error": ["NoNodesForSelectionCriteria"]}' |
Running dbt expecting Fusion when we are in a venv | Use dbtf or ~/.local/bin/dbt |
| Schema errors after changing files in Fusion | Run dbt clean to clear the stale schema cache, then re-run |
Adding LIMIT to SQL in dbt_show | Use limit parameter instead |
| Vars with special characters | Pass as simple string, no \ or \n |
--select my_model # Single model
--select staging.* # Path pattern
--select fqn:*stg_* # FQN pattern
--select model_a model_b # Union (space)
--select tag:x,config.mat:y # Intersection (comma)
--exclude my_model # Exclude from selection--resource-type model
--resource-type test --resource-type unit_testdbt list --select my_model+ # Preview selection
dbt list --select my_model+ --resource-type model # Only models
dbt list --output json # JSON output
dbt list --select my_model --output json --output-keys unique_id name resource_type configdbt show --select my_model --limit 10
dbt show --inline "select * from {{ ref('orders') }} where status = 'pending'" --limit 5--vars 'my_var: value' # Single
--vars '{"k1": "v1", "k2": 42, "k3": true}' # Multiple (JSON)# Quick status check
cat target/run_results.json | jq '.results[] | {node: .unique_id, status: .status, time: .execution_time}'
# Find failures
cat target/run_results.json | jq '.results[] | select(.status != "success")'dbt build --select my_model --defer --state prod-artifactsdbt build --select my_model --defer --state prod-artifacts --favor-statedbt run --static-analysis=off
dbt run --static-analysis=unsafe