- Home
- Skills
- Data & Databases
- dbt Project Check
More screenshots
Works with the AI Agents you already use
dbt Project Check
This skill finds those and the other dbt mistakes below, and tells you how to fix each one.
$5
dbt Project Check
Example session with this skill installed
Check this project with dbt-project-check.
- Read your context and instructions
- Compiled the dbt project check
$ python3 scripts/check_dbt.py examples/risky
BLOCK dbt_project.yml:16 D03 SECRET_IN_PROJECT_FILE
geocoder_api_key=<redacted, 22 chars>
Why: A git token or password is written into a package URL in packages.yml or dependencies.yml (https://TOKEN@github.com/...), or a var with a secret name has a literal value in dbt_project.yml. These files are always committed, so everyone who can read the repository gets the token, and dbt_project.yml values can end up in compiled SQL and dbt's metadata artifacts.
Safer: Change the token, then read it at run time: git: "https://{{ env_var('DBT_ENV_SECRET_GIT_CREDENTIAL') }}@github.com/org/repo.git" in packages.yml, or use native private packages (private: org/repo). Pass secret vars with --vars or env_var() instead of writing them down.
BLOCK packages.yml:4 D03 SECRET_IN_PROJECT_FILE
BLOCK profiles.yml:10 D01 SECRET_IN_PROFILES_YML
BLOCK profiles.yml:10 D02 PROFILES_YML_NOT_GITIGNORED
BLOCK profiles.yml:28 D01 SECRET_IN_PROFILES_YML
REVIEW models/marts/fct_orders.sql:1 D11 MODEL_WITHOUT_KEY_TESTS
REVIEW models/marts/fct_orders.sql:3 D15 INCREMENTAL_WITHOUT_UNIQUE_KEY
REVIEW models/marts/fct_orders.sql:17 D14 HARDCODED_RELATION
REVIEW models/staging/_shop__sources.yml:4 D13 SOURCE_WITHOUT_FRESHNESS
REVIEW models/staging/stg_shop__orders.sql:7 D12 SELECT_STAR_FROM_SOURCE
REVIEW profiles.yml:19 D16 DEFAULT_PASSWORD_IN_PROFILES_YML
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 9 files, 9 with dbt project content.
This is a static check of file text. NOT FLAGGED is not a guarantee.
Connects securely to your tools. The creator never sees your data.
About this skill
A profiles.yml copied into the repository for CI with the warehouse password still in it, or a packages.yml that installs a private package from https://ghp_...@github.com, hands your warehouse or GitHub access to everyone who can read the repo. Quieter mistakes break the numbers instead: an incremental model without a unique_key stores late rows twice, and a model with no unique test on its key lets a bad join multiply rows. This skill finds those and the other dbt mistakes below, and tells you how to fix each one.
Your agent runs a scanner on your dbt project: dbt_project.yml, every profiles.yml in the folder (also .dbt/profiles.yml), packages.yml, dependencies.yml, and the SQL models and YAML properties files in your model-paths. It knows dbt's Jinja (ref(), source(), config(), env_var(), is_incremental()), both tests: and data_tests:, freshness and loaded_at_field under config: (dbt 1.9 and 1.10), configs set in config(), a properties file or a dbt_project.yml folder block, and your .gitignore. It follows dbt's own style guide, so import CTEs, select * from final and select * from a ref() are not reported. It never runs dbt or connects to your warehouse. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.
What it checks
BLOCK
- D01: literal passwords, tokens, private keys, keyfile_json, client secrets, refresh tokens and AWS secret keys in profiles.yml (also real-looking secrets used as env_var() defaults)
- D02: a profiles.yml with literal credentials in a git repository that no .gitignore rule or .git/info/exclude entry covers
- D03: git tokens or passwords in packages.yml and dependencies.yml URLs, and key-like secret vars written in dbt_project.yml
REVIEW
- D11: models with no unique + not_null test pair on a key column (or no properties file at all); time-spine models are skipped
- D12: a final select * (or a lone t.*) that passes every raw column of a source() or a named table straight through
- D13: sources whose tables have no freshness with warn_after or error_after
- D14: database.schema.table or schema.table written out instead of ref() or source()
- D15: incremental models without a unique_key (append, insert_overwrite, microbatch and Databricks replace_where are fine)
- D16: env_var() fallbacks to a well-known default password such as postgres or changeme in profiles.yml
What's included
- The scanner (Python 3.9+, standard library only)
- A rules guide with the reason and safer approach for each rule
- A risky and a safe example dbt project, and the real report the scanner produces on the risky one
Limits It reads files as written. Jinja is not rendered, so models built by macros or loops, configs set from var() or env_var(), and adapter defaults are not evaluated. A profiles.yml in ~/.dbt/ is checked only when you name it, and a global git excludes file is not read. Python models, seeds, snapshots, analyses, singular tests and installed packages in dbt_packages/ are not checked. A primary_key constraint alone does not count as a key test, because most warehouses do not enforce it. NOT FLAGGED is not a guarantee.
Static check of dbt project text. Jinja is not rendered; Python models, seeds, snapshots and installed packages are not checked. NOT FLAGGED is not a guarantee.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 5 days ago
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example project includes clearly fake, inert passwords and tokens (NOTREAL) for the scanner to find. Nothing connects to a warehouse.