D
dbt-transformation-patterns
About dbt-transformation-patterns
A dbt-focused skill for designing and maintaining data transformation projects. It covers model organization, testing, documentation, incremental processing, and run optimization for warehouse-backed workflows.
Key features
- 01Layered model organization
- 02Data quality tests
- 03Documentation and freshness checks
- 04Incremental model strategies
- 05Selectors and CI optimization
Use cases
- 01Structuring dbt transformation projects
- 02Adding tests and freshness checks
- 03Processing large datasets incrementally
- 04Optimizing dbt runs in CI
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ sickn33/ agentic-awesome-skills --skill dbt-transformation-patternsAfter installing, type/dbt-transformation-patternsin Claude Code to confirm it loaded.
Bundled filesresources/implementation-playbook.md
Details
From the project READMEdbt Transformation Patterns
Production-ready patterns for dbt (data build tool) including model organization, testing strategies, documentation, and incremental processing.
Use this skill when
- Building data transformation pipelines with dbt
- Organizing models into staging, intermediate, and marts layers
- Implementing data quality tests and documentation
- Creating incremental models for large datasets
- Setting up dbt project structure and conventions
Do not use this skill when
- The project is not using dbt or a warehouse-backed workflow
- You only need ad-hoc SQL queries
- There is no access to source data or schemas
Instructions
- Define model layers, naming, and ownership.
- Implement tests, documentation, and freshness checks.
- Choose materializations and incremental strategies.
- Optimize runs with selectors and CI workflows.
- If detailed patterns are required, open
resources/implementation-playbook.md.
Resources
resources/implementation-playbook.mdfor detailed dbt patterns and examples.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Comments
Markdown supported