dagster
Dagster skills for CLI operations, best practices, and integrations. Dagster+ MCP server included for direct access to your deployment data.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 11 Nov 2026.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/dagster-io/skills with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/dagster-io/skills'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/dagster-io-skills)HTML
<a href="/listings/dagster-io-skills"><img src="/api/listings/dagster-io-skills/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
Claude Code
Install using the [Claude plugin marketplace](https://code.claude.com/docs/en/discover-plugins#add-from-github):
/plugin marketplace add dagster-io/skills /plugin install dagster@dagster /dagster-expert "What's an asset?"
Auto-update is off by default for third-party marketplaces. To pick up new releases without reinstalling, run `/plugin`, open **Marketplaces**, select `dagster`, and enable auto-update.
The plugin includes the [Dagster+ MCP server](https://docs.dagster.io/getting-started/ai-tools/dagster-mcp), giving the skill direct access to your deployed organization: runs, assets, deployments, code locations, alert policies, Issues, and insights metrics. Run `/mcp` to authenticate.
/mcp # authenticate dagster-plus Fetch the run logs for the most recent run failure.
The MCP URL points at the US region by default. If your organization is in the EU region, set the following environment variable before launching Claude Code:
export DAGSTER_CLOUD_MCP_URL=https://mcp.agent.eu.dagster.cloud/mcp
Using `npx skills`
Install using the [`npx skills`](https://skills.sh/) command-line:
npx skills add dagster-io/skills#release-stable
This installs the skill into every agent it detects (Claude Code, Codex, Cursor, Copilot, OpenCode, Pi, and others). It copies skills only; the bundled MCP server is not configured this way.
OpenAI Codex
Codex reads the same marketplace manifest as Claude Code:
codex plugin marketplace add dagster-io/skills --ref release-stable codex plugin add dagster@dagster
GitHub Copilot CLI
Copilot's marketplace schema has no `git-subdir` source, so install the plugin directly:
copilot plugin install dagster-io/skills:plugins/dagster
This tracks `master`; Copilot has no documented way to target a branch.
Manual Installation
<details> <summary>See full instructions...</summary>
Clone the repository and copy skills to your tool's skills directory:
**OpenCode:**
git clone --branch release-stable https://github.com/dagster-io/skills.git cp -r skills/plugins/dagster/skills/* ~/.config/opencode/skill/
**Pi Agent:**
git clone --branch release-stable https://github.com/dagster-io/skills.git cp -r skills/plugins/dagster/skills/* ~/.pi/agent/skills/
</details>
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
.claude-plugin/marketplace.json · Manifest · 24 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- {
- "name": "dagster",
- "owner": {
- "name": "Dagster"
- },
- "description": "Dagster skills for CLI operations, best practices, and integrations. Dagster+ MCP server included for direct access to your deployment data.",
- "plugins": [
- {
- "name": "dagster",
- "source": {
- "source": "git-subdir",
- "url": "https://github.com/dagster-io/skills.git",
- "path": "plugins/dagster",
- "ref": "release-stable"
- },
- "description": "Comprehensive Dagster development conventions and best practices, with the Dagster+ MCP server bundled for querying your deployment."
- },
- {
- "name": "dagster-expert",
- "source": "./plugins/dagster-expert",
- "description": "Deprecated. Install dagster@dagster instead, then uninstall this plugin."
- }
- ]
- }
README.md · README · 181 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- <div align="center">
- <img width="auto" height="38px" alt="dagster-hearts-claude" src="https://github.com/user-attachments/assets/b162dddf-6a7e-459e-be06-29d34d637650" />
- </div>
- # Dagster Skills
- AI assistant skills for building workflows and data pipelines using Dagster. It bundles the `dagster-expert` skill for authoring pipelines and the [Dagster+ MCP server](https://docs.dagster.io/getting-started/ai-tools/dagster-mcp) for access to your Dagster+ deployment.
- **Compatible with Claude Code, Cursor, OpenAI Codex, GitHub Copilot, OpenCode, Pi, and other Agent Skills-compatible tools.**
- All install paths below deliver the `release-stable` branch, which moves to each weekly Dagster
- release. The `dagster` marketplace entry itself points at that branch, so the marketplace can be
- added from `master` and still install released content.
- ## Installation
- ### Claude Code
- Install using the
- [Claude plugin marketplace](https://code.claude.com/docs/en/discover-plugins#add-from-github):
- ```
- /plugin marketplace add dagster-io/skills
- /plugin install dagster@dagster
- /dagster-expert "What's an asset?"
- ```
- Auto-update is off by default for third-party marketplaces. To pick up new releases without
- reinstalling, run `/plugin`, open **Marketplaces**, select `dagster`, and enable auto-update.
- The plugin includes the
- [Dagster+ MCP server](https://docs.dagster.io/getting-started/ai-tools/dagster-mcp), giving the skill direct
- access to your deployed organization: runs, assets, deployments, code locations, alert policies,
- Issues, and insights metrics. Run `/mcp` to authenticate.
- ```
- /mcp
- # authenticate dagster-plus
- Fetch the run logs for the most recent run failure.
- ```
- The MCP URL points at the US region by default. If your organization is in the EU region, set the following environment variable before launching Claude Code:
- ```bash
- export DAGSTER_CLOUD_MCP_URL=https://mcp.agent.eu.dagster.cloud/mcp
- ```
- ### Using `npx skills`
- Install using the [`npx skills`](https://skills.sh/) command-line:
- ```bash
- npx skills add dagster-io/skills#release-stable
- ```
- This installs the skill into every agent it detects (Claude Code, Codex, Cursor, Copilot, OpenCode,
- Pi, and others). It copies skills only; the bundled MCP server is not configured this way.
- ### OpenAI Codex
- Codex reads the same marketplace manifest as Claude Code:
- ```bash
- codex plugin marketplace add dagster-io/skills --ref release-stable
- codex plugin add dagster@dagster
- ```
- ### GitHub Copilot CLI
- Copilot's marketplace schema has no `git-subdir` source, so install the plugin directly:
- ```bash
- copilot plugin install dagster-io/skills:plugins/dagster
- ```
- This tracks `master`; Copilot has no documented way to target a branch.
- ### Manual Installation
- <details>
- <summary>See full instructions...</summary>
- Clone the repository and copy skills to your tool's skills directory:
- **OpenCode:**
- ```bash
- git clone --branch release-stable https://github.com/dagster-io/skills.git
- cp -r skills/plugins/dagster/skills/* ~/.config/opencode/skill/
- ```
- **Pi Agent:**
- ```bash
- git clone --branch release-stable https://github.com/dagster-io/skills.git
- cp -r skills/plugins/dagster/skills/* ~/.pi/agent/skills/
- ```
- </details>
- ## Upgrading from `dagster-expert`
- The Dagster skill now ships in a plugin named `dagster` rather than `dagster-expert`. The skill
- itself is unchanged and is still invoked with `/dagster-expert`.
- `dagster-expert` remains installable for now, but has become a stub that carries no Dagster guidance and only points here. To migrate:
- ```
- /plugin install dagster@dagster
- /plugin uninstall dagster-expert
- ```
- If you install `dagster` without uninstalling `dagster-expert`, two plugins
- provide a skill named `dagster-expert` and the deprecated stub may be used instead of the real one.
- The `dagster-expert` plugin will be removed in a future release. After that, installations of it
- report `Plugin dagster-expert not found in marketplace dagster` and stop loading.
- ## 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=high
- ```
- ## Dagster+ MCP
- Direct access to Dagster+ data about your deployment, including run logs, Insights, and select actions to remediate failures.
- The MCP server uses your user permissions when determining the MCP server permissions. To use custom permissions, see the documentation for alternative authentication methods [here](https://docs.dagster.io/getting-started/ai-tools/dagster-mcp#connecting-to-the-mcp-server)
- **What you can do:**
- - Launch runs, materialize assets, re-run runs and backfills
- - Fetch run logs
- - Fetch asset definitions and metadata
- - Fetch deployments and deployment information.
- - Create and update alert policies and fetch their notifications
- - Fetch Insights metrics for assets, jobs, and deployments
- **Example prompts:**
- ```
- Fetch the logs for run <run id>, investigate why it failed, and propose a solution.
- What is the materialization success rate over the past month?
- How often has the customer_returns_job failed in the past quarter?
- What assets in my deployment are not covered by an alert policy?
- ```
- ## Contributing
- See [CONTRIBUTING.md](./CONTRIBUTING.md).
- <div align="center">
- <img alt="dagster logo" src="https://github.com/user-attachments/assets/6fbf8876-09b7-4f4a-8778-8c0bb00c5237" width="auto" height="16px">
- </div>
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.