[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77JGYMV99B50EXENBZ72QDM":3,"skill-same:01M77JGYMV99B50EXENBZ72QDM":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M77JGYMV99B50EXENBZ72QDM","dagster-workflows",null,"Route Dagster intent to Seshat's governed medallion workflow or the official Dagster competence owner without bypassing readiness, approvals, or evidence.","Kemetra\u002FSeshat-BI","Kemetra","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206601658?v=4","01M77J5APND9QAJK8XMBH5B1A8","01M77J5AR4TM1GN2G4GS5KH02J",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FKemetra\u002FSeshat-BI\u002Fblob\u002Fmain\u002Fdistribution\u002Fbundle-templates\u002Fshared\u002Fskills\u002Fdagster-workflows\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: dagster-workflows\ndescription: >-\n  Route Dagster intent to Seshat's governed medallion workflow or the official\n  Dagster competence owner without bypassing readiness, approvals, or evidence.\n---\n\n# Governed Dagster workflows\n\nRead `..\u002F..\u002Fportable-operating-contract.md` before acting. For a governed\nSeshat medallion run, use only the installed `seshat dagster` helpers; never\ninvoke `dagster` directly against the orchestration project and never bypass\nthe gate readers, the closed-argv runner, or the redaction layer. Dagster RUNS\nalready-approved steps; the gate exit code and the named human decide whether\na stage passed.\n\n## Intent ownership\n\n| User intent | Seshat pre-gate | Execution owner | Seshat afterward |\n|---|---|---|---|\n| Decide whether orchestration fits the BI workflow | Readiness state and orchestration assessment | Seshat selection policy | State one truthful next action |\n| Run the governed medallion graph | Per-asset readiness, evidence, and named-human approval gates | Dagster through `seshat dagster` | Record derived run evidence, blockers, and the earliest truthful next action |\n| Author assets, jobs, resources, components, or project structure | Prove the official skill is activated and discoverable | Official `dagster-expert` skill | If the project enters Seshat's governed flow, return through the Seshat gates above |\n| Design schedules, sensors, or declarative automation | Prove the official skill is activated and discoverable | Official `dagster-expert` skill | Keep Seshat automations stopped until a named human starts them |\n| Generic Dagster CLI guidance, validation, or troubleshooting | Prove the official skill is activated and discoverable | Official `dagster-expert` skill | Do not infer a readiness effect from native success |\n| Publish a Power BI result | `publish_ready: pass` and the separate publish adapter gate | Official Power BI executor when available | Dagster records the trigger result and never publishes itself |\n\nSpec 148 provides the read-only harness proof for the official `dagster-expert`\nskill. Before routing generic competence, run\n`seshat integrations setup --profile orchestration --harness \u003Cclaude-code|codex>`\nand require the `dagster-agent-skills` result to be discoverable. Otherwise report\nthe exact upstream-integration blocker. Do not copy official guidance into this\nrouter, claim an installed payload is usable, or invoke native Dagster commands\nagainst the governed project as a fallback.\n\n## Fixed workflow\n\n1. Preflight read-only, without a database query:\n\n   `seshat dagster doctor --json`\n\n   Report blockers verbatim with their remediation hints. Database\n   credentials are reported present\u002Fabsent only -- never echo a connection\n   value. An absent DSN is a deferred boundary, not a failure to hide.\n\n2. Execute one governed job as a shell-free child process in the\n   orchestration project's own environment:\n\n   `seshat dagster run --job \u003Cfull_sequence_job|through_gold_job> [--table \u003Ctable>] [--source-mode \u003Ccsv|existing-bronze>] [--json]`\n\n   `--source-mode` selects the Bronze origin (the gated tail is identical for\n   both and is never bypassed):\n\n   - `csv` (default): a raw `\u003Ctable>.csv` lands and the loader OWNS and\n     reloads `bronze.\u003Ctable>` (drop-and-reload). Use it for a file-first\n     workspace. This is the one destructive-by-design mode.\n   - `existing-bronze`: NON-DESTRUCTIVE DB-first. An already-loaded\n     `bronze.\u003Ctable>` is verified READ-ONLY (existence, row count, and that its\n     columns cover the approved source-map) and used as the satisfied\n     upstream. It issues ZERO Bronze DDL\u002FDML. Use it when Bronze already lives\n     in the warehouse (BCP, COPY, an external ETL, a prior tool); never export\n     Bronze to a CSV just to feed the default path. `raw_source_file` records a\n     `deferred` boundary (no landing file by design), not a failure. A missing,\n     empty, or source-map-mismatched relation fails closed with a named blocker.\n\n   The chosen mode is explicit in the command result and in the run evidence\n   (`bronze_table`'s measured facts). Any doctor blocker stops the run before\n   anything executes. A failed or blocked gate halts every downstream asset\n   fail-closed; report the recorded `blocking_reason` and its named owner, then\n   stop.\n\n3. List runs or render the committed derived record:\n\n   `seshat dagster evidence [--run-id \u003Cid>] [--json]`\n\n   The committed record is written by that verb as\n   `orchestration\u002Fdagster\u002Frun-evidence\u002F\u003Crun-id>.md`, rendered deterministically\n   from the raw records. Never edit raw records or rendered evidence by hand.\n\n## Hard boundaries\n\n- A green asset means \"the command ran and returned this exit code\" -- NEVER\n  \"the stage is now pass\". Readiness passes come only from the gate exit code\n  and a named human; this adapter records, it does not decide.\n- The shipped schedule and sensor are STOPPED by default; starting either is\n  a named-human action, never an agent default.\n- Publishing is walled off: the graph only TRIGGERS the publish feature and\n  fails closed while it is absent. Never publish or simulate publishing.\n- Without database credentials, DB-touching assets record a deferred boundary\n  and block fail-closed. Report that truthfully; never fabricate a run,\n  an asset result, or run evidence.\n- Never write a readiness pass, an approval, a confidence score, raw adapter\n  output, a credential, a DSN, or an absolute local path.\n\n## Exit meanings\n\n- exit 0: command completed; run evidence remains derived, not an approval.\n- exit 1: usage error (unknown verb or flag).\n- exit 2: preflight or gate refusal -- doctor blockers, a gate not CLEARED, a\n  missing prerequisite, or evidence records refused schema validation\n  (nothing executed).\n- exit 3: the run failed or halted fail-closed on a gate (the CI signal);\n  evidence is still rendered and must be reported.\n- exit 4: unexpected internal error, already redacted; report it verbatim --\n  it is not a fixable evidence-record problem.\n","# Governed Dagster workflows\n\nRead `..\u002F..\u002Fportable-operating-contract.md` before acting. For a governed\nSeshat medallion run, use only the installed `seshat dagster` helpers; never\ninvoke `dagster` directly against the orchestration project and never bypass\nthe gate readers, the closed-argv runner, or the redaction layer. Dagster RUNS\nalready-approved steps; the gate exit code and the named human decide whether\na stage passed.\n\n## Intent ownership\n\n| User intent | Seshat pre-gate | Execution owner | Seshat afterward |\n|---|---|---|---|\n| Decide whether orchestration fits the BI workflow | Readiness state and orchestration assessment | Seshat selection policy | State one truthful next action |\n| Run the governed medallion graph | Per-asset readiness, evidence, and named-human approval gates | Dagster through `seshat dagster` | Record derived run evidence, blockers, and the earliest truthful next action |\n| Author assets, jobs, resources, components, or project structure | Prove the official skill is activated and discoverable | Official `dagster-expert` skill | If the project enters Seshat's governed flow, return through the Seshat gates above |\n| Design schedules, sensors, or declarative automation | Prove the official skill is activated and discoverable | Official `dagster-expert` skill | Keep Seshat automations stopped until a named human starts them |\n| Generic Dagster CLI guidance, validation, or troubleshooting | Prove the official skill is activated and discoverable | Official `dagster-expert` skill | Do not infer a readiness effect from native success |\n| Publish a Power BI result | `publish_ready: pass` and the separate publish adapter gate | Official Power BI executor when available | Dagster records the trigger result and never publishes itself |\n\nSpec 148 provides the read-only harness proof for the official `dagster-expert`\nskill. Before routing generic competence, run\n`seshat integrations setup --profile orchestration --harness \u003Cclaude-code|codex>`\nand require the `dagster-agent-skills` result to be discoverable. Otherwise report\nthe exact upstream-integration blocker. Do not copy official guidance into this\nrouter, claim an installed payload is usable, or invoke native Dagster commands\nagainst the governed project as a fallback.\n\n## Fixed workflow\n\n1. Preflight read-only, without a database query:\n\n   `seshat dagster doctor --json`\n\n   Report blockers verbatim with their remediation hints. Database\n   credentials are reported present\u002Fabsent only -- never echo a connection\n   value. An absent DSN is a deferred boundary, not a failure to hide.\n\n2. Execute one governed job as a shell-free child process in the\n   orchestration project's own environment:\n\n   `seshat dagster run --job \u003Cfull_sequence_job|through_gold_job> [--table \u003Ctable>] [--source-mode \u003Ccsv|existing-bronze>] [--json]`\n\n   `--source-mode` selects the Bronze origin (the gated tail is identical for\n   both and is never bypassed):\n\n   - `csv` (default): a raw `\u003Ctable>.csv` lands and the loader OWNS and\n     reloads `bronze.\u003Ctable>` (drop-and-reload). Use it for a file-first\n     workspace. This is the one destructive-by-design mode.\n   - `existing-bronze`: NON-DESTRUCTIVE DB-first. An already-loaded\n     `bronze.\u003Ctable>` is verified READ-ONLY (existence, row count, and that its\n     columns cover the approved source-map) and used as the satisfied\n     upstream. It issues ZERO Bronze DDL\u002FDML. Use it when Bronze already lives\n     in the warehouse (BCP, COPY, an external ETL, a prior tool); never export\n     Bronze to a CSV just to feed the default path. `raw_source_file` records a\n     `deferred` boundary (no landing file by design), not a failure. A missing,\n     empty, or source-map-mismatched relation fails closed with a named blocker.\n\n   The chosen mode is explicit in the command result and in the run evidence\n   (`bronze_table`'s measured facts). Any doctor blocker stops the run before\n   anything executes. A failed or blocked gate halts every downstream asset\n   fail-closed; report the recorded `blocking_reason` and its named owner, then\n   stop.\n\n3. List runs or render the committed derived record:\n\n   `seshat dagster evidence [--run-id \u003Cid>] [--json]`\n\n   The committed record is written by that verb as\n   `orchestration\u002Fdagster\u002Frun-evidence\u002F\u003Crun-id>.md`, rendered deterministically\n   from the raw records. Never edit raw records or rendered evidence by hand.\n\n## Hard boundaries\n\n- A green asset means \"the command ran and returned this exit code\" -- NEVER\n  \"the stage is now pass\". Readiness passes come only from the gate exit code\n  and a named human; this adapter records, it does not decide.\n- The shipped schedule and sensor are STOPPED by default; starting either is\n  a named-human action, never an agent default.\n- Publishing is walled off: the graph only TRIGGERS the publish feature and\n  fails closed while it is absent. Never publish or simulate publishing.\n- Without database credentials, DB-touching assets record a deferred boundary\n  and block fail-closed. Report that truthfully; never fabricate a run,\n  an asset result, or run evidence.\n- Never write a readiness pass, an approval, a confidence score, raw adapter\n  output, a credential, a DSN, or an absolute local path.\n\n## Exit meanings\n\n- exit 0: command completed; run evidence remains derived, not an approval.\n- exit 1: usage error (unknown verb or flag).\n- exit 2: preflight or gate refusal -- doctor blockers, a gate not CLEARED, a\n  missing prerequisite, or evidence records refused schema validation\n  (nothing executed).\n- exit 3: the run failed or halted fail-closed on a gate (the CI signal);\n  evidence is still rendered and must be reported.\n- exit 4: unexpected internal error, already redacted; report it verbatim --\n  it is not a fixable evidence-record problem.\n",{"name":5,"description":7},"main","6266e304556a72b75d951b9433fd833481c61233","distribution\u002Fbundle-templates\u002Fshared\u002Fskills\u002Fdagster-workflows",0,"https:\u002F\u002Fgithub.com\u002FKemetra\u002FSeshat-BI","https:\u002F\u002Fpypi.org\u002Fproject\u002Fseshat-bi\u002F","https:\u002F\u002Fgithub.com\u002FKemetra","2026-11-11 21:44:25",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Kemetra\u002FSeshat-BI --skill dagster-workflows",{"tool":37,"command":38},"bunx","bunx skills add Kemetra\u002FSeshat-BI --skill dagster-workflows",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Kemetra\u002FSeshat-BI --skill dagster-workflows","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FKemetra\u002FSeshat-BI\u002Fblob\u002Fmain\u002Fdistribution\u002Fbundle-templates\u002Fshared\u002Fskills\u002Fdagster-workflows\u002FSKILL.md",true,[],[46,53,58,64,69,76],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M77JWCTJ88JWPDD25WZ2NEY8","fake-skill","A fixture skill with declaring frontmatter, used as positive shipped evidence.","https:\u002F\u002Fgithub.com\u002FKemetra\u002FSeshat-BI\u002Fblob\u002Fmain\u002Ftests\u002Funit\u002Ffixtures\u002Fcapability_inventory\u002Funlisted\u002F.claude\u002Fskills\u002Ffake-skill\u002FSKILL.md",[],[],{"skillNo":54,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":18},"01M77JWA0BTG4JB2HR52Q99216","https:\u002F\u002Fgithub.com\u002FKemetra\u002FSeshat-BI\u002Fblob\u002Fmain\u002Ftests\u002Funit\u002Ffixtures\u002Fcapability_inventory\u002Forphan\u002F.claude\u002Fskills\u002Ffake-skill\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M77JW6VE59XEFHWBTNDYAS2Q","bare-skill-no-frontmatter","https:\u002F\u002Fgithub.com\u002FKemetra\u002FSeshat-BI\u002Fblob\u002Fmain\u002Ftests\u002Funit\u002Ffixtures\u002Fcapability_inventory\u002Forphan\u002F.claude\u002Fskills\u002Fbare-skill-no-frontmatter\u002FSKILL.md",[],[],{"skillNo":65,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":18},"01M77JW4TD1FNFSBNP5C0WXAA5","https:\u002F\u002Fgithub.com\u002FKemetra\u002FSeshat-BI\u002Fblob\u002Fmain\u002Ftests\u002Funit\u002Ffixtures\u002Fcapability_inventory\u002Fgood\u002F.claude\u002Fskills\u002Ffake-skill\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":18},"01M77JVWCVE3WZ82ZNFCSFVDCP","retail-kpi-knowledge","Retail KPI \u002F metric-contract reasoning layer for BI agents in the Seshat BI project. Use when an agent must reason about the BUSINESS MEANING of a retail KPI before any implementation — defining a KPI in business terms, classifying additivity (fully\u002Fsemi\u002Fnon-additive), identifying grain, listing required source fields, resolving ambiguity (gross vs net, VAT, returns, cost method, same-store), choosing an MVP KPI pack, reviewing a metric contract for completeness, or preparing a clean handoff to an implementation layer. Also use it to classify KPI sufficiency or prepare an owner policy decision packet. This is a meaning\u002Fdefinition + review layer, not an executor: it does not write DAX\u002FSQL\u002FPython, grant readiness, approve policy, or design dashboards. See INDEX.md for live\u002Fplanned routes; registry.yaml is the authoritative machine-readable inventory.","https:\u002F\u002Fgithub.com\u002FKemetra\u002FSeshat-BI\u002Fblob\u002Fmain\u002Fskills\u002Fretail-kpi-knowledge\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M77JVNDM1NGYGSCPTBW9ZCF5","bi-sql-knowledge","SQL reasoning, validation, reconciliation, transformation, diagnostics, and anti-pattern knowledge layer for Seshat BI agents. Use when a task involves reasoning about source SQL: source profiling, table grain, keys & uniqueness, joins & fan-out amplification, aggregation correctness, COUNT\u002FNULL semantics, deduplication, validation queries, reconciliation queries, silver\u002Fgold transformation logic, window\u002Fdate-time analytics, SQL anti-patterns, or basic SQL performance reasoning, or interpretation of a supplied sanitized PostgreSQL JSON execution plan. The SQL counterpart to bi-dax-knowledge. It is a thinking & validation layer, not a database executor, runtime validator, dbt\u002FDagster project, or automatic tuning service.","https:\u002F\u002Fgithub.com\u002FKemetra\u002FSeshat-BI\u002Fblob\u002Fmain\u002Fskills\u002Fbi-sql-knowledge\u002FSKILL.md",[],[]]