How do I install the Dbt Principal Engineer skill?

Run npx skillmds@latest add modra40/dbt-principal-engineer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Dbt Principal Engineer safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Dbt Principal Engineer?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Dbt Principal Engineer free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Dbt Principal Engineer?

modra40 (@modra40) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Dbt Principal Engineer by modra40 — Agent Skill

Name: Dbt Principal Engineer
Author: modra40

Dbt Principal Engineer

Principal/Senior-level dbt playbook for analytics engineering architecture, model design, testing, lineage, governance, and operating trustworthy transformation platforms at scale. Use when: designing dbt projects, reviewing model and domain boundaries, governing analytics transformations, or operating dbt in production workflows.

modra40 0c9dcc5 9 files · 9.3 KB Updated Sep 17, 2026

File contents

dbt Mastery (Senior → Principal)

Operate

Start from data product boundaries, lineage trust, and transformation ownership.
Treat dbt as analytics engineering infrastructure, not only SQL templating.
Prefer clear model layers, documented contracts, and governance over convenience sprawl.
Optimize for trustworthy semantics, maintainability, and platform supportability.

Default Standards

Model boundaries should reflect domain ownership and consumer intent.
Tests and documentation must support trust, not vanity coverage.
Macros should reduce repetition without hiding logic.
Environments and runs should align with deployment and governance policy.
dbt should enable governed self-service, not analytics chaos.

References

Project architecture and model layering: references/project-architecture-and-model-layering.md
Testing, contracts, and trust signals: references/testing-contracts-and-trust-signals.md
Macros, packages, and abstraction discipline: references/macros-packages-and-abstraction-discipline.md
Lineage, ownership, and data product governance: references/lineage-ownership-and-data-product-governance.md
Environments, deployment, and run safety: references/environments-deployment-and-run-safety.md
Warehouse economics and performance discipline: references/warehouse-economics-and-performance-discipline.md
Reliability and operations: references/reliability-and-operations.md
Incident runbooks: references/incident-runbooks.md

---name: dbt-principal-engineerdescription: Principal/Senior-level dbt playbook for analytics engineering architecture, model design, testing, lineage, governance, and operating trustworthy transformation platforms at scale. Use when: designing dbt projects, reviewing model and domain boundaries, governing analytics transformations, or operating dbt in production workflows.---# dbt Mastery (Senior → Principal)## Operate- Start from data product boundaries, lineage trust, and transformation ownership.- Treat dbt as analytics engineering infrastructure, not only SQL templating.- Prefer clear model layers, documented contracts, and governance over convenience sprawl.- Optimize for trustworthy semantics, maintainability, and platform supportability.## Default Standards- Model boundaries should reflect domain ownership and consumer intent.- Tests and documentation must support trust, not vanity coverage.- Macros should reduce repetition without hiding logic.- Environments and runs should align with deployment and governance policy.- dbt should enable governed self-service, not analytics chaos.## References- Project architecture and model layering: [references/project-architecture-and-model-layering.md](references/project-architecture-and-model-layering.md)- Testing, contracts, and trust signals: [references/testing-contracts-and-trust-signals.md](references/testing-contracts-and-trust-signals.md)- Macros, packages, and abstraction discipline: [references/macros-packages-and-abstraction-discipline.md](references/macros-packages-and-abstraction-discipline.md)- Lineage, ownership, and data product governance: [references/lineage-ownership-and-data-product-governance.md](references/lineage-ownership-and-data-product-governance.md)- Environments, deployment, and run safety: [references/environments-deployment-and-run-safety.md](references/environments-deployment-and-run-safety.md)- Warehouse economics and performance discipline: [references/warehouse-economics-and-performance-discipline.md](references/warehouse-economics-and-performance-discipline.md)- Reliability and operations: [references/reliability-and-operations.md](references/reliability-and-operations.md)- Incident runbooks: [references/incident-runbooks.md](references/incident-runbooks.md)

Frequently asked questions