Setting the issue. One moment.
Contents
Issue No. 96Dagster · Official
dagster-io /skills
A collection of AI skills for working with Dagster
2 chapters · 5 minutes · 1,127 words
Install and provenance
npx skills add dagster-io/skills/plugin marketplace add dagster-io/skills- Owner
- dagster-io · Organization
- Licence
- Apache-2.0
- Last updated
- Published from
- github.com/
dagster-io/ skills
Front matter
From the READMEDagster Skills
AI assistant skills for building workflows and data pipelines using Dagster.
Compatible with Claude Code, Cursor, OpenCode, OpenAI Codex, Pi, and other Agent Skills-compatible tools.
Installation
Claude Code
Install using the Claude plugin marketplace (opens in a new tab):
/plugin marketplace add dagster-io/skills
/plugin install dagster-expert@dagster
/dagster-expert "What's an asset?"Using npx skills
Install using the npx skills (opens in a new tab) command-line:
npx skills add dagster-io/skillsManual Installation
Clone the repository and copy skills to your tool’s skills directory:
OpenCode:
git clone https://github.com/dagster-io/skills.git
cp -r skills/skills/* ~/.config/opencode/skill/OpenAI Codex:
git clone https://github.com/dagster-io/skills.git
cp -r skills/skills/* ~/.codex/skills/Pi Agent:
git clone https://github.com/dagster-io/skills.git
cp -r skills/skills/* ~/.pi/agent/skills/Skills
dagster-expert
Expert guidance for building production-quality Dagster projects, covering CLI commands, asset patterns, automation strategies, and implementation workflows.
What you can do:
- Create and scaffold projects, assets, schedules, and sensors
- Understand asset patterns (dependencies, partitions, multi-assets, metadata)
- Implement automation (declarative automation, schedules, sensors)
- Use CLI commands (launch, list, check, scaffold, logs)
- Design project structure and configure environments
- Follow implementation workflows and best practices
- Debug issues and validate project configuration
Example prompts:
Create a new Dagster project called analytics
How do I scaffold a new asset?
Show me how to set up declarative automation
What's the proper way to partition my assets?
Help me debug why my materialization failed
How should I structure my project for multiple pipelines?
Launch all assets tagged with priority=highdignified-python
Production-quality Python coding standards for modern Python.
Use for general Python code quality, not Dagster-specific patterns.
What’s included:
- Modern type syntax (list[str], str | None)
- LBYL exception handling patterns
- Pathlib operations
- Python version-specific features (3.10-3.13)
- CLI patterns (Click, argparse)
- Advanced typing patterns
- Interface design (ABC, Protocol)
- API design principles
Example questions:
Is this good Python code?
How should I annotate this function?
What's the difference between LBYL and EAFP?
Should I use pathlib or os.path?Contributing
Colophon
How this issue was made- Source
- github.com/dagster-io/skills, branch
master, last pushed 7 August 2026. - Licence
- Apache-2.0 — the text of every chapter is reproduced unmodified, frontmatter included, under the upstream licence.
- Discovery
- 2 chapters found by walking the repository tree for
SKILL.md, not by matching a directory convention. 2 distinct layouts observed:skills/dagster-expert/skills/*/SKILL.md,skills/dignified-python/skills/*/SKILL.md. - Issue colours
- Resolved from a deterministic hash of the owner name. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.
- Heading repairs
- 1 repair applied to the front matter so the document has one
h1and no skipped levels:- Shifted “9 headings” from h1 to h2 so the chapter title is the only h1.
- Spec compliance
- Every chapter satisfies the Agent Skills specification’s frontmatter rules.
- Images
- Images inside a chapter come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.
- Marketplace
- A plugin manifest is published at
.claude-plugin/marketplace.jsonby Colton Padden, declaring 2 plugins. It is read for editorial metadata only — never as the skill index, which is always the repository tree. - Signal
- Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.
- Agent surfaces
- The whole issue is available as one markdown document at
/dagster-io/skills.md, and each chapter at its own.mdURL. - Publication
- Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.