dagster-orchestration-adapter

Runs approved medallion pipeline steps unattended in CI as a Dagster asset graph.

2|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/Kemetra/Seshat-BI --skill dagster-orchestration-adapter-kemetra
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dagster-orchestration-adapter
Source: https://github.com/Kemetra/Seshat-BI/tree/main/.claude/skills/dagster-orchestration-adapter
Command: npx skills add https://github.com/Kemetra/Seshat-BI --skill dagster-orchestration-adapter-kemetra

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires dagster.

What problem does it solve? Running a multi-stage retail data medallion pipeline (bronze, silver, gold, semantic model, publish) by hand in CI is error-prone and risks skipping required human approvals. This Skill orchestrates the already-approved sequence unattended as a Dagster asset graph, enforcing every gate and recording run evidence without ever self-approving a stage. ## Core Features & Use Cases - Gated asset graph execution: Runs an 11-asset Dagster graph where each asset executes only after its gate (gate exit code or committed human approval) is satisfied, and fails closed otherwise. - Human-seam enforcement: Halts at mapping approval, judgment calls (grain, PII, rollup), and the publish wall, escalating to a named human instead of auto-resolving. - Derived run evidence: Writes per-run records with per-asset exit codes, outcomes, blocking reasons, and named owners, without ever marking a readiness stage as passed. - Use Case: A data team wants nightly CI runs of their retail warehouse pipeline. They use this Skill so Dagster executes only approved steps, stops at unapproved mapping gates, and produces auditable run evidence for each run. ## Quick Start Ask the agent to run the Dagster medallion pipeline for a table using the seshat dagster run command after confirming the mapping gate is cleared.

Frequently Asked Questions about dagster-orchestration-adapter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run the medallion pipeline unattended with Dagster?▼

Use the seshat dagster run command with a job such as full_sequence_job or through_gold_job, optionally scoped to a table. Each asset runs only after its gate is satisfied, and a failed gate halts downstream assets and exits non-zero for CI.

What is the difference between Dagster orchestration and retail-orchestrate?▼

retail-orchestrate is the interactive conductor of the medallion sequence, while the Dagster adapter is its unattended CI sibling running the same sequence. Both respect the same gate-exit authority and human seams, and neither self-approves a stage.

Can Dagster publish the Power BI model directly?▼

No. The adapter is DB-connected, not publish-capable. The terminal asset only triggers the separate F016 publish adapter once publish_ready is pass, and fails closed if F016 is absent.

What happens when a gate fails during a Dagster run?▼

The failed gate asset halts, all downstream assets are recorded as skipped, and the Dagster run terminates with a failed status so CI surfaces the blocker. The run-evidence record captures the concrete blocking reason and named owner.

Why does the Dagster run block without database credentials?▼

DB-touching assets require credentials from a git-ignored .env file such as DATABASE_URL. Without them, assets record a deferred boundary and block fail-closed rather than fabricating a successful run.