What is slack-dagster-to-orchestra?

A migration guide for changing Dagster notifications into equivalent Orchestra alerts or Slack-sending tasks. Dagster is a data-pipeline tool, while Orchestra is another platform for building and running those pipelines.

Converting Dagster failure and success sensors, hooks, and in-operation Slack messages into Orchestra configurations.

It clarifies whether each Slack message belongs as a status alert or as a step placed at a specific point in the pipeline.

slack-dagster-to-orchestra — Skill for Claude Code by orchestra-hq

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add orchestra-hq/orchestra-skills --skill slack-dagster-to-orchestra

Clone the repo

git clone --depth 1 https://github.com/orchestra-hq/orchestra-skills

Made for: Claude Code.

Or install migrate-to-orchestra, the plugin that ships this one along with the rest of its 52 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/slack-dagster-to-orchestra/github.svg)](https://agentmods.dev/skills/orchestra-hq/orchestra-skills/slack-dagster-to-orchestra)

Your own site

<a href="https://agentmods.dev/skills/orchestra-hq/orchestra-skills/slack-dagster-to-orchestra"><img src="https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/slack-dagster-to-orchestra/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/orchestra-hq/orchestra-skills/slack-dagster-to-orchestra"><img src="https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/slack-dagster-to-orchestra.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 105 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,729 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00105	$0.01729
Opus 5.5	$0.00042	$0.00692
Sonnet 5.5	$0.00021	$0.00346
Haiku 4.5	$0.00011	$0.00173

Measured 1mo ago against content hash c0bc52eaa9f6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

slack-dagster-to-orchestra scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/migrate-to-orchestra/skills/slack-dagster-to-orchestra/SKILL.md · 179 lines

How it starts

The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Slack: Dagster -> Orchestra Conversion

Overview

Dagster Slack notifications come in two forms:

Run-status sensors / hooks (make_slack_on_run_failure_sensor, @failure_hook, @success_hook) — fire when a run or op changes status; not pipeline steps.
Explicit messages inside an op (context.resources.slack.get_client().chat_postMessage(...)) — a message sent at a specific point in the run.

In Orchestra these map to:

alerts block (pipeline-level or task-level) — fires on status change; no pipeline slot consumed.
SLACK pipeline task (integration: SLACK, integration_job: SEND_SLACK_MESSAGE) — fires at a specific position, when content depends on runtime logic or ordering matters.

Decision Guide

Dagster pattern	Orchestra equivalent
`make_slack_on_run_failure_sensor`	Pipeline-level `alerts` block (`statuses: [FAILED]`)
`@failure_hook` / `@success_hook` on whole job	Pipeline-level `alerts` block
`@failure_hook` / `@success_hook` on a single op	Task-level `alerts` block on that task
`SlackResource.chat_postMessage` inside an op (mid-run)	`SLACK` + `SEND_SLACK_MESSAGE` task
Slack message at end of job	Pipeline-level `alerts` block (`statuses: [SUCCEEDED]`)

Option 1: Orchestra Alerts (YAML) — recommended for sensors & hooks

AlertModel schema

Field	Required	Notes
`name`	yes	Unique within scope
`statuses`	yes	`FAILED`, `SUCCEEDED`, `CANCELLED`, `WARNING`, `SKIPPED`
`destinations`	yes	One entry per channel/target
`custom_message`	no	Appended to the standard Orchestra alert message

AlertDestinationModel

Field	Value / notes
`integration`	`SLACK`, `EMAIL`, `PAGER_DUTY`, `WEBHOOK`, `MICROSOFT_TEAMS`
`destination`	Channel name (e.g. `#data-alerts`) — required for Slack
`connection_id`	Required for PagerDuty, Teams, Webhook

version: v1
name: my-pipeline

alerts:
  - name: on-failure-slack
    statuses:
      - FAILED
    destinations:
      - integration: SLACK
        destination: '#data-alerts'
    custom_message: 'Check the logs and rerun from the failed task.'

pipeline:
  stage-001:
    tasks:
      task-001:
        # ... your tasks here

Read the full file on GitHub · 179 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago Changed c0bc52eaa9f6
2mo ago First seen · 179 lines · 105 tokens per session scan A e490bb976795

Subscribe to this mod's changes

slack-dagster-to-orchestra is a skill published in the GitHub repository orchestra-hq/orchestra-skills (9 stars, last pushed yesterday), licensed MIT. It adds 105 tokens to every session and 1,729 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

DevOps and cloud

slack-dagster-to-orchestra next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
slack-dagster-to-orchestraorchestra-hq/orchestra-skills	Skill	9	yesterday	MIT	A	105	Claude Code
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code