dagster-assets

Define and automate Dagster asset materialization with dependencies and partitions.

14|1|Updated May 5, 2026
One-click install
npx skills add https://github.com/ivanshamaev/de-agent-skills --skill dagster-assets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dagster-assets
Source: https://github.com/ivanshamaev/de-agent-skills/tree/main/skills/dagster_assets
Command: npx skills add https://github.com/ivanshamaev/de-agent-skills --skill dagster-assets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dagster Software-Defined Assets (SDA) solve the problem of organizing data pipeline logic as explicit, dependency-tracked, materialized data objects instead of ad-hoc scripts and opaque job steps.

Core Features & Use Cases

  • Asset-based pipeline structure: define persistent data objects (tables/files/models) with clear lineage between upstream and downstream assets.
  • Partitioned materialization: implement daily, static, multi-dimensional, and dynamic partitions so you recompute only what’s needed.
  • Automation and triggering: use sensors and schedules, plus declarative automation with AutomationCondition (eager/on_cron/on_missing) to materialize assets reliably.
  • Custom IO management: control how asset outputs are stored/loaded (for example, Parquet on S3) and capture output metadata.
  • Multi-asset outputs: produce multiple dependent assets from a single operation using @multi_asset.
  • Resources and deployment wiring: inject external connections via ConfigurableResource and structure Definitions for deployment.

Quick Start

Activate this skill by telling your AI to generate a Dagster project that defines @asset and partitioned assets, wires a custom S3 Parquet IO manager, and adds sensors/schedules for materialization.

Frequently Asked Questions about dagster-assets

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

FAQPage Schema
How do I model data pipelines as software-defined assets in Dagster?

To model data pipelines as Dagster software-defined assets, you define persistent data objects using @asset and @multi_asset functions, establishing clear lineage between upstream and downstream assets for dependency-tracked materialization.

How do I configure partitioned backfills for Dagster assets?

Configure partitioned backfills in Dagster by implementing daily, static, multi-dimensional, or dynamic partitions on your assets, ensuring you only recompute materialized data for the specific partitions needed.

How does declarative automation work for triggering Dagster asset materialization?

Declarative automation in Dagster triggers asset materialization by configuring AutomationCondition policies like eager, on_cron, or on_missing, replacing manual schedules with reliable, event-driven runs for your data workflows.

How do I use a custom IO manager to store Dagster asset outputs as Parquet files on S3?

Use a custom IO manager in Dagster to control how asset outputs are stored and loaded, such as configuring it to save materialized data as Parquet files on S3 while capturing output metadata.

Can I produce multiple dependent assets from a single operation in Dagster?

Yes, you can produce multiple dependent assets from a single operation in Dagster by using the @multi_asset decorator, allowing one function to yield several persistent data objects with clear lineage.

How do I inject external connections into Dagster asset definitions?

Inject external connections into Dagster asset definitions by using ConfigurableResource to wire external services and structuring your Definitions object for deployment.