Skill

drt-create-sync

From drt

Generates drt sync YAML configuration files for Reverse ETL pipelines, connecting data warehouse tables via dbt refs or SQL to destinations like Slack, Discord, REST APIs, HubSpot, GitHub Actions, Google Sheets, PostgreSQL, or MySQL.

dbt

PostgreSQL

MySQL

data-engineering

npx claudepluginhub drt-hub/drt --plugin drt

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Create a drt sync YAML configuration file for the user.

SKILL.md

Similar Skills

drt-create-sync

Generates drt sync YAML configuration files for Reverse ETL pipelines, syncing data warehouse tables via dbt refs or SQL to destinations like Slack, APIs, databases, or Jira.

drt-hub

setting-up-a-data-warehouse-source

Guides connecting data warehouse sources like Postgres, MySQL, Stripe, HubSpot, MongoDB, Salesforce, BigQuery, Snowflake to PostHog via wizard, credential validation, table discovery, sync selection, and creation.

1 file

posthog

flux-pipeline

Build a data pipeline — ETL/ELT with extraction, transformation, loading, error handling, and scheduling. Use when asked to "build ETL", "data pipeline", "move data from X to Y", or "sync data".

11 tools

tonone

Stats

Parent Repo Stars11

Parent Repo Forks13

Last CommitApr 2, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Create a drt sync YAML configuration file for the user.

Steps

Ask the user for the following (or infer from context if already provided):
- Source table or SQL: what data to sync (e.g. ref('new_users') or a SQL query)
- Destination: where to send it (Slack, Discord, REST API, HubSpot, GitHub Actions, Google Sheets, PostgreSQL, MySQL, or other)
- Sync mode: full (every run) or incremental (watermark-based, needs a cursor column)
- Frequency intent: helps set batch_size and rate_limit
Generate a valid sync YAML using the exact field names from docs/llm/API_REFERENCE.md.
Output the YAML in a code block and suggest where to save it: syncs/<name>.yml

Show the command to validate and run it:

drt validate
drt run --select <name> --dry-run
drt run --select <name>

Rules

Use type: bearer + token_env (never hardcode tokens)
Default on_error: skip for Slack/webhooks, on_error: fail for critical syncs
For incremental mode, always include cursor_field
Use ref('table_name') when the source is a single DWH table; raw SQL when filtering or joining
Jinja2 templates use {{ row.<column_name> }} — column names must come from the user

Reference

See docs/llm/API_REFERENCE.md for all fields, types, and defaults.