dbt-write

Enforce dbt write patterns for column naming and type preservation.

475|25|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/SignalPilot-Labs/SignalPilot --skill dbt-write
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dbt-write
Source: https://github.com/SignalPilot-Labs/SignalPilot/tree/main/benchmark/signalpilot-plugin/skills/dbt-write
Command: npx skills add https://github.com/SignalPilot-Labs/SignalPilot --skill dbt-write

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent application of dbt write patterns across models leads to drift in column naming, data types, join defaults, and materialization decisions. This Skill centralizes enforcement of best practices to produce predictable, auditable dbt artifacts.

Core Features & Use Cases

  • Column naming & type preservation: Enforce exact column names from YML contracts, preserve source types when no reference exists, and ensure consistent casting across models.
  • Join defaults & materialization: Standardize left/right joins, COALESCE for metrics, and correct materialization strategies per use case.
  • Siblings & lookup patterns: Promote pattern reuse across sibling models and correct lookup fan-out handling.
  • Grain consistency & ref usage: Validate grain and rely on ref models for shared metrics to avoid recomputing.

Quick Start

Apply the project’s dbt-write conventions when adding or updating a model to ensure consistent naming, typing, and join logic.

Frequently Asked Questions about dbt-write

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce consistent column naming and data types in dbt models?

Enforce consistent dbt column naming and type preservation by applying centralized write patterns that validate exact names from YML contracts and preserve source types when no reference exists.

What is the best way to standardize join logic and materialization in dbt?

Standardize dbt join logic and materialization by enforcing consistent left/right joins, applying COALESCE for metrics, and selecting correct materialization strategies per use case.

How do I handle lookup fan-out and reuse patterns across sibling dbt models?

Handle dbt lookup fan-out and sibling patterns by applying standardized write rules that promote pattern reuse across sibling models and ensure correct fan-out validation.

Can I automate dbt write discipline for surrogate keys and rounding behavior?

Automate dbt write discipline for surrogate keys and rounding behavior by applying validation rules across models to ensure predictable, auditable artifacts and consistent data quality.

Why does my dbt model drift from established write patterns and contracts?

dbt model drift occurs when write patterns are applied inconsistently across models, which this approach solves by centralizing enforcement of naming, typing, join logic, and materialization decisions.