Skip to content
Back to search

dagster

MarketplaceWorks with Claude CodeGitHub

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.

Checked today

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
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/dagster-io-skills/badge.svg)](/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)

  1. {
  2. "name": "dagster",
  3. "owner": {
  4. "name": "Dagster"
  5. },
  6. "description": "Dagster skills for CLI operations, best practices, and integrations. Dagster+ MCP server included for direct access to your deployment data.",
  7. "plugins": [
  8. {
  9. "name": "dagster",
  10. "source": {
  11. "source": "git-subdir",
  12. "url": "https://github.com/dagster-io/skills.git",
  13. "path": "plugins/dagster",
  14. "ref": "release-stable"
  15. },
  16. "description": "Comprehensive Dagster development conventions and best practices, with the Dagster+ MCP server bundled for querying your deployment."
  17. },
  18. {
  19. "name": "dagster-expert",
  20. "source": "./plugins/dagster-expert",
  21. "description": "Deprecated. Install dagster@dagster instead, then uninstall this plugin."
  22. }
  23. ]
  24. }
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)

  1. <div align="center">
  2. <img width="auto" height="38px" alt="dagster-hearts-claude" src="https://github.com/user-attachments/assets/b162dddf-6a7e-459e-be06-29d34d637650" />
  3. </div>
  4. # Dagster Skills
  5. 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.
  6. **Compatible with Claude Code, Cursor, OpenAI Codex, GitHub Copilot, OpenCode, Pi, and other Agent Skills-compatible tools.**
  7. All install paths below deliver the `release-stable` branch, which moves to each weekly Dagster
  8. release. The `dagster` marketplace entry itself points at that branch, so the marketplace can be
  9. added from `master` and still install released content.
  10. ## Installation
  11. ### Claude Code
  12. Install using the
  13. [Claude plugin marketplace](https://code.claude.com/docs/en/discover-plugins#add-from-github):
  14. ```
  15. /plugin marketplace add dagster-io/skills
  16. /plugin install dagster@dagster
  17. /dagster-expert "What's an asset?"
  18. ```
  19. Auto-update is off by default for third-party marketplaces. To pick up new releases without
  20. reinstalling, run `/plugin`, open **Marketplaces**, select `dagster`, and enable auto-update.
  21. The plugin includes the
  22. [Dagster+ MCP server](https://docs.dagster.io/getting-started/ai-tools/dagster-mcp), giving the skill direct
  23. access to your deployed organization: runs, assets, deployments, code locations, alert policies,
  24. Issues, and insights metrics. Run `/mcp` to authenticate.
  25. ```
  26. /mcp
  27. # authenticate dagster-plus
  28. Fetch the run logs for the most recent run failure.
  29. ```
  30. 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:
  31. ```bash
  32. export DAGSTER_CLOUD_MCP_URL=https://mcp.agent.eu.dagster.cloud/mcp
  33. ```
  34. ### Using `npx skills`
  35. Install using the [`npx skills`](https://skills.sh/) command-line:
  36. ```bash
  37. npx skills add dagster-io/skills#release-stable
  38. ```
  39. This installs the skill into every agent it detects (Claude Code, Codex, Cursor, Copilot, OpenCode,
  40. Pi, and others). It copies skills only; the bundled MCP server is not configured this way.
  41. ### OpenAI Codex
  42. Codex reads the same marketplace manifest as Claude Code:
  43. ```bash
  44. codex plugin marketplace add dagster-io/skills --ref release-stable
  45. codex plugin add dagster@dagster
  46. ```
  47. ### GitHub Copilot CLI
  48. Copilot's marketplace schema has no `git-subdir` source, so install the plugin directly:
  49. ```bash
  50. copilot plugin install dagster-io/skills:plugins/dagster
  51. ```
  52. This tracks `master`; Copilot has no documented way to target a branch.
  53. ### Manual Installation
  54. <details>
  55. <summary>See full instructions...</summary>
  56. Clone the repository and copy skills to your tool's skills directory:
  57. **OpenCode:**
  58. ```bash
  59. git clone --branch release-stable https://github.com/dagster-io/skills.git
  60. cp -r skills/plugins/dagster/skills/* ~/.config/opencode/skill/
  61. ```
  62. **Pi Agent:**
  63. ```bash
  64. git clone --branch release-stable https://github.com/dagster-io/skills.git
  65. cp -r skills/plugins/dagster/skills/* ~/.pi/agent/skills/
  66. ```
  67. </details>
  68. ## Upgrading from `dagster-expert`
  69. The Dagster skill now ships in a plugin named `dagster` rather than `dagster-expert`. The skill
  70. itself is unchanged and is still invoked with `/dagster-expert`.
  71. `dagster-expert` remains installable for now, but has become a stub that carries no Dagster guidance and only points here. To migrate:
  72. ```
  73. /plugin install dagster@dagster
  74. /plugin uninstall dagster-expert
  75. ```
  76. If you install `dagster` without uninstalling `dagster-expert`, two plugins
  77. provide a skill named `dagster-expert` and the deprecated stub may be used instead of the real one.
  78. The `dagster-expert` plugin will be removed in a future release. After that, installations of it
  79. report `Plugin dagster-expert not found in marketplace dagster` and stop loading.
  80. ## Skills
  81. ### `dagster-expert`
  82. Expert guidance for building production-quality Dagster projects, covering CLI commands, asset patterns, automation strategies, and implementation workflows.
  83. **What you can do:**
  84. - Create and scaffold projects, assets, schedules, and sensors
  85. - Understand asset patterns (dependencies, partitions, multi-assets, metadata)
  86. - Implement automation (declarative automation, schedules, sensors)
  87. - Use CLI commands (launch, list, check, scaffold, logs)
  88. - Design project structure and configure environments
  89. - Follow implementation workflows and best practices
  90. - Debug issues and validate project configuration
  91. **Example prompts:**
  92. ```
  93. Create a new Dagster project called analytics
  94. How do I scaffold a new asset?
  95. Show me how to set up declarative automation
  96. What's the proper way to partition my assets?
  97. Help me debug why my materialization failed
  98. How should I structure my project for multiple pipelines?
  99. Launch all assets tagged with priority=high
  100. ```
  101. ## Dagster+ MCP
  102. Direct access to Dagster+ data about your deployment, including run logs, Insights, and select actions to remediate failures.
  103. 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)
  104. **What you can do:**
  105. - Launch runs, materialize assets, re-run runs and backfills
  106. - Fetch run logs
  107. - Fetch asset definitions and metadata
  108. - Fetch deployments and deployment information.
  109. - Create and update alert policies and fetch their notifications
  110. - Fetch Insights metrics for assets, jobs, and deployments
  111. **Example prompts:**
  112. ```
  113. Fetch the logs for run <run id>, investigate why it failed, and propose a solution.
  114. What is the materialization success rate over the past month?
  115. How often has the customer_returns_job failed in the past quarter?
  116. What assets in my deployment are not covered by an alert policy?
  117. ```
  118. ## Contributing
  119. See [CONTRIBUTING.md](./CONTRIBUTING.md).
  120. <div align="center">
  121. <img alt="dagster logo" src="https://github.com/user-attachments/assets/6fbf8876-09b7-4f4a-8778-8c0bb00c5237" width="auto" height="16px">
  122. </div>

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.