home / skills / dagster-io / skills / dagster-integrations

dagster-integrations skill

safe

/skills/dagster-integrations/skills/dagster-integrations

This skill helps you discover and understand Dagster integration libraries to streamline tool connections and enhance data workflows.

npx playbooks add skill dagster-io/skills --skill dagster-integrations

Review the files below or copy the command above to add this skill to your agents.

Files (17)

SKILL.md

3.2 KB

---
name: dagster-integrations
description:
  Skill that helps users discover and understand Dagster integration libraries. Used when users have requests related to
  integrating with other tools / technologies, or when have users have questions related to specific integration
  libraries (dagster-*).
---

# Dagster Integrations Skill

This skill is a thin wrapper around more complex and detailed reference documents. It helps guide users through workflows that require using or understanding Dagster integration libraries.

## Workflow Decision Tree

Depending on the user's request, choose the appropriate reference file:

- Using a specific integration library?
  - Try to find a `references/dagster-<technology>/` folder in this directory. This will be named directly after the integration library name (e.g. `dagster-dbt`, `dagster-fivetran`, `dagster-airbyte`, etc.). This folder will contain a `README.md` file that will contain references to more detailed reference files relevant to the specific request.
  - If no such folder exists, use the more general reference files outlined in the `Reference Files Index` section.
  - **Examples**:
    - "How do asset checks work with dagster-dbt?"
    - "Load my Fivetran connector into Dagster"
    - "Can I use Tableau with Dagster?"
  - **NOTE**: If the user is attempting to use a specific integration library for the first time (often the case when adding a new component to a project), ensure the integration library is installed in the project before scaffolding the component.
    - `uv`-compatible projects (most common): `uv add dagster-<technology>`
- General integration requests?
  - Use the more general reference files outlined in the `Reference Files Index` section.
  - **Examples**:
    - "How do I load data from a CSV file into Dagster?"
    - "What data quality tools does Dagster support?"

These reference files contain detailed instructions specific to the given workflow. If it is unclear which reference file to use, ask the user to clarify their request.

Note that some requests may require multiple reference files in order to complete.

## Reference Files Index

- [ai.md](./references/ai.md)
  - Contains information related to all integrations that are related to AI and ML.
- [etl.md](./references/etl.md)
  - Contains information related to all integrations that are related to ETL and ELT.
- [storage.md](./references/storage.md)
  - Contains information related to all integrations that are related to data storage.
- [compute.md](./references/compute.md)
  - Contains information related to all integrations that are related to compute.
- [bi.md](./references/bi.md)
  - Contains information related to all integrations that are related to BI and visualization.
- [monitoring.md](./references/monitoring.md)
  - Contains information related to all integrations that are related to monitoring and observability.
- [alerting.md](./references/alerting.md)
  - Contains information related to all integrations that are related to alerting and notifications.
- [testing.md](./references/testing.md)
  - Contains information related to all integrations that are related to testing and data quality.
- [dagster-dbt/README.md](./references/dagster-dbt/README.md)
  - Contains information related to the dagster-dbt integration library.

Overview

This skill helps you discover and understand Dagster integration libraries and how to use them in data orchestration workflows. It guides decision making about which integration to use, points to targeted reference material, and provides practical steps for first-time setup and common tasks. Use it when you need concise direction about dagster-* libraries or general integration patterns with Dagster.

How this skill works

I inspect the user request to decide whether a specific dagster-<technology> integration is relevant or if a general integration reference is a better fit. For specific integrations I point to the relevant integration folder and README that contains detailed, task-focused instructions. For general integration questions I consult topic-based reference files (ETL, storage, compute, BI, monitoring, alerts, testing, AI) and synthesize the next steps.

When to use it

You want to add or scaffold a component that uses a concrete dagster-<technology> library (e.g., dagster-dbt, dagster-airbyte).
You need installation guidance or must confirm an integration is present in your project before scaffolding.
You have a general integration question about how Dagster connects to storage, compute, or BI systems.
You need help discovering which Dagster integration best fits a workflow (ETL, monitoring, AI/ML pipelines).
You want examples or pointers for common tasks like loading CSVs, running dbt assets, or sending alerts from Dagster.

Best practices

Identify whether a dedicated dagster-<technology> package exists; prefer official integrations when available.
Install the integration into your project before generating scaffolded components (e.g., uv add dagster-<technology> for uv-compatible projects).
Map your workflow to a reference topic (ETL, storage, compute, BI, monitoring, alerts, testing, AI) before starting implementation.
Combine multiple reference files when workflows span areas (for example, ETL + storage + monitoring).
If unclear which reference applies, ask clarifying questions about the tools, desired outcome, and whether the integration is already installed.

Example use cases

Walkthrough to add dagster-dbt and wire dbt models as Dagster assets with checks and schedules.
Guidance to load a Fivetran connector into Dagster and trigger syncs as part of an ELT pipeline.
Advice on connecting common storage backends (S3, GCS, local filesystem) for intermediate data in Dagster pipelines.
Recommendations for integrating monitoring and alerting tools so pipeline failures trigger notifications.
High-level patterns for adding AI/ML integrations and where to find specialized references for model training and inference.

FAQ

What if I can’t find a dagster-<technology> folder for my tool?

Use the general topic references (ETL, storage, compute, etc.) and I’ll suggest equivalent patterns or alternative integrations. If you plan to add that integration, ensure it is installed first.

Do you scaffold code or install packages automatically?

I provide concrete commands and scaffold templates and will remind you to install the integration. Actual installation or code changes must be run by you or your tooling.