dbt_ingest
FeaturedMap dbt `schema.yml` / `properties.yml` models and sources into ktx semantic-layer overlays and column notes. Covers `sources:` vs `models:`, column `data_tests` (not_null, unique, accepted_values, relationships), and how bundle-time writes complement manifest backfill from git sync. Load when the WorkUnit's `skillNames` includes `dbt_ingest` or when raw files are dbt YAML under `models/` / `sources/`.
Install
Quality Score: 94/100
Skill Content
Details
- Author
- Kaelio
- Repository
- Kaelio/ktx
- Created
- 2 months ago
- Last Updated
- 1 weeks ago
- Language
- TypeScript
- License
- Apache-2.0
Similar Skills
Semantically similar based on skill content — not just same category
dbt-patterns
dbt model design, ref chains, sources, tests, macros, incremental strategies, materializations, and documentation best practices. Use this skill whenever the user is writing or reviewing dbt models, configuring dbt tests, designing model layers (staging/intermediate/marts), asking about incremental models, choosing materializations, writing macros, setting up sources.yml, or troubleshooting dbt run/test failures. Also trigger when the user mentions dbt refs, lineage graphs, model dependencies, dbt Cloud, the dbt CLI, or when they want to transform data already in the warehouse using SQL. If the project uses dbt at all, this skill should be active for any transformation questions.
testing-dbt-models
Adds schema tests and data quality validation to dbt models. Use when working with dbt tests for: (1) Adding or modifying tests in schema.yml files (2) Task mentions "test", "validate", "data quality", "unique", "not_null", or "accepted_values" (3) Ensuring data integrity - primary keys, foreign keys, relationships (4) Debugging test failures or understanding why dbt test failed Matches existing project test patterns and YAML style before adding new tests.
build-dbt-model
Skill builder. Reads your existing dbt models to extract the company's actual best practices — naming, layering, tests, materialisations, SQL style — then interviews your team about the rules the code cannot show, and generates a custom /new-model skill that scaffolds dbt models indistinguishable from your best existing ones. Use when new models keep failing review for convention reasons, or when every analyst writes dbt in their own dialect.