Agent skill · dagster-io
dagster-expert
Expert guidance for working with Dagster and the dg CLI. ALWAYS use before doing any task that requires knowledge specific to Dagster, or that references assets, materialization, components, data tools or data pipelines. Common tasks may include creating a new project, adding new definitions, understanding the current project structure, answering general questions about the codebase (finding asset, schedule, sensor, component or job definitions), debugging issues, or providing deep information about a specific Dagster concept.
What it needs
About 4k tokens when loaded.
What this skill does
Core Dagster Concepts Brief definitions only (see reference files for detailed examples): Asset: Persistent object (table, file, model) produced by your pipeline Component: Reusable building block that generates definitions (assets, schedules, sensors, jobs, etc.) relevant to a particular domain. Integration Workflow When integrating with ANY external tool or service, read the Integration libraries index. This contains information about which integration libraries exist, and references on how to create new custom integrations for tools that do not have a published library. Programmatic Access: dg CLI and the Dagster Plus MCP server There are two ways to interact with Dagster programmatically. Pick by where the work happens: The dg CLI — everything in the local project: adding definitions, scaffolding, validating, exploring project structure, and launching runs locally. Installed as part of the dagster-dg-cli package. If a relevant CLI command for a local task exists, always attempt to use it. The Dagster Plus MCP server — querying and managing a deployed Dagster Plus organization: runs, assets, deployments, code locations, alert policies, Issues, and insights metrics. When it is connected, prefer its tools over the equivalent dg api commands. dg api covers the same deployed resources as the MCP server from the command line, and remains the way to reach the parts the server does not expose. Before doing anything against a deployed Dagster Plus environment, read Dagster Plus API: General — it covers how to choose between the two and how to fall back safely. ONLY explore the existing project structure if it is strictly necessary to accomplish the user's goal. In many cases, existing CLI tools will have sufficient understanding of the project structure, meaning listing and reading existing files is wasteful and unnecessary. Almost all dg commands that return information have a --json flag that can be used to get the information in a machine-readable format. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills dagster-io/dagster-expert--9d7d92