dbt-projects-snowflake-setup_skill

This skill guides you through setting up dbt projects on Snowflake from prerequisites to automated scheduling and monitoring.

Python

26

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill sfc-gh-dflippo/snowflake-dbt-demo --skill dbt-projects-snowflake-setup

SKILL.md12.1 KB

Overview

This skill is a step-by-step setup guide for dbt Projects on Snowflake, covering prerequisites, integrations, event table monitoring, and automated scheduling. It focuses on practical SQL and UI steps to enable package downloads, Git access, workspace creation, deployment, and task scheduling. Use it to get a production-ready dbt on Snowflake environment with monitoring and secure integrations.

How this skill works

The guide walks through enabling a personal database, creating an external access integration for dbt package downloads, and creating API integrations for Git providers. It shows how to create a Snowsight workspace from a Git repo, configure profiles.yml for Snowflake execution, deploy a DBT PROJECT object, and set up event tables and Snowflake Tasks for scheduling. Troubleshooting tips and verification queries are included to validate each step.

When to use it

Setting up dbt Projects on Snowflake for the first time
Configuring external network access for dbt deps and package installs
Integrating GitHub/GitLab/Azure DevOps with Snowflake workspaces
Adding event table monitoring for dbt Project telemetry
Scheduling automated dbt runs with Snowflake Tasks
Troubleshooting workspace creation, package downloads, or event capture

Best practices

Enable personal databases and use ACCOUNTADMIN only for initial setup
Create external access and API integrations with minimal allowed prefixes
Set event tables at the DATABASE level for project isolation and clear telemetry
Keep profiles.yml account/user empty to rely on Snowflake context; specify warehouse/database/schema/role
Use separate integrations/warehouses for dev and prod; rotate PATs and use minimal scopes

Example use cases

CI/CD: Deploy a dbt project from Git and run dbt build via a Snowflake Task on a schedule
Monitoring: Route dbt execution logs to a centralized event table and query recent failures
Onboarding: Create Snowsight workspaces for developers using a shared API integration and PAT
Troubleshooting: Verify external access and API integrations when dbt deps or Git access fails
Environment segregation: Maintain separate databases and event tables for dev and prod dbt projects

FAQ

Database-level event tables capture all project executions for that database, provide project isolation, and avoid account-wide noise or missed cross-schema events.

What hosts must external access allow for dbt deps?

Include hub.getdbt.com and codeload.github.com (or provider-specific hosts) so dbt can download packages and Git-hosted sources.

What scopes are required for a PAT?

GitHub: repo scope. GitLab: read_repository. Azure DevOps: Code (Read). Use minimal scopes and rotate tokens regularly.