Skip to content
Back to skills

Dagster Expert

ASecurity

The user is running the deprecated `dagster-expert` plugin. It no longer carries the Dagster skill — that now ships in the `dagster` plugin.

  • 203 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added February 7, 2026
devops

Works with

  • claude code
  • cursor
  • cli

Security analysis

A100/100

Pro scans all 20 files and shows the line behind each finding

Scanned September 20, 2026

npx -y skills add dagster-io/skills --skill dagster-expert --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Dagster Expert?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Dagster Expert
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/dagster-io-dagster-expert/badge)](https://www.skillsdirectory.com/skills/dagster-io-dagster-expert)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: dagster-expert
description:
  Use for any task involving Dagster, the dg CLI, assets, materialization, components, data tools or data
  pipelines, matching the situations the Dagster skill handles. This is the deprecated dagster-expert
  plugin. It carries no Dagster guidance and exists only to tell the user to move to the dagster plugin.
---

## This plugin has been replaced

The user is running the deprecated `dagster-expert` plugin. It no longer carries the Dagster skill — that now ships in the `dagster` plugin.

Do not answer the user's Dagster question from memory. Tell them to run:

```
/plugin install dagster@dagster

/plugin uninstall dagster-expert
```
if they are in a Claude code session. If they are in a Cursor session, instruct them to uninstall the current Dagster plugin and re-install it.

Both commands matter. Installing `dagster` without uninstalling `dagster-expert` leaves two plugins providing a skill named `dagster-expert`, and this deprecated one may be chosen instead of the real one. If the user reaches this notice after already installing `dagster`, that is what has happened — have them uninstall `dagster-expert` and retry.

Nothing else changes: the skill keeps the name `dagster-expert` and is still invoked as `/dagster-expert`.

Files in this skill

  • SKILL.md9.8 KB
  • references/asset-key-design.md8.4 KB
  • references/assets.md12.7 KB
  • references/automation/README.md2.9 KB
  • references/automation/declarative-automation/README.md2.3 KB
  • references/automation/declarative-automation/advanced.md7.2 KB
  • references/automation/declarative-automation/core-concepts.md4.4 KB
  • references/automation/declarative-automation/customization.md4.3 KB
  • references/automation/declarative-automation/operands.md5.7 KB
  • references/automation/declarative-automation/operators.md4.5 KB
  • references/automation/schedules.md3.7 KB
  • references/automation/sensors/README.md1.7 KB
  • references/automation/sensors/asset-sensors.md3.5 KB
  • references/automation/sensors/basic-sensors.md3.3 KB
  • references/automation/sensors/run-status-sensors.md3.3 KB
  • references/cli/api.md1007 B
  • references/cli/asset-selection.md3.2 KB
  • references/cli/check.md1.3 KB
  • references/cli/launch.md2.4 KB
  • references/cli/list.md3.3 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.