CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dagster-io-managers-to-orchestra

Use this skill when a Dagster project passes data between ops/assets via return values, Out/In wiring, IO managers, or context.add_output_metadata, and you need that data flow represented in Orchestra. Triggers: any op/asset that returns a value consumed downstream, any custom or built-in IOManager, any use of Output(value, metadata=...), AssetMaterialization metadata, or MetadataValue used to surface values to downstream logic.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplary translation-guide body: nearly every token carries Orchestra- or Dagster-specific knowledge Claude would not have, with executable YAML/Python examples, exact reference syntax, a supported-integration matrix, and precise gotchas including the triple-quote JSON-escaping trap. Minor improvements would be trimming the tangential Alerts section and the duplicated set_output import caveat.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious, Orchestra-specific facts (auto-injected ORCHESTRA_API_KEY, hyphenated task IDs, triple-quote JSON escaping) and avoids explaining concepts Claude already knows, fitting anchor 4 (efficient, minor trims possible). It falls short of 5 because the 'Adding Alerts' section is tangential to data passing and the set_output-method-vs-bare-function caveat is repeated in both the Overview and the Gotchas.

4 / 5

Actionability

Guidance is fully executable and copy-paste ready: complete YAML stage/task blocks, runnable Python using OrchestraSDK, exact reference syntax "${{ ORCHESTRA.PIPELINE_RUN_TASKS['task_id'].OUTPUTS['key'] }}", a supported-integrations table with exact integration_job and field names, and a full before/after worked example covering the common cases (SQL auto-capture, SDK call, condition branching). This matches anchor 5; there are no pseudocode gaps that would pull it to 4.

5 / 5

Workflow Clarity

The conversion sequence is clear and well-ordered — identify the Dagster pattern (mapping table), set outputs upstream, reference them downstream, then apply gotchas — and the Before/After example walks the full flow end to end, fitting anchor 4. It does not reach 5 because there is no verification checkpoint (e.g., confirming an output was registered or a condition evaluated), though this config-translation task is neither destructive nor batch, so no cap applies.

4 / 5

Progressive Disclosure

The skill has no bundle files, and the ~185-line body is cleanly sectioned (Overview, Pattern Mapping, examples, integrations table, Gotchas, References) with external doc links clearly signaled in a References section — good structure with content appropriately inline, matching anchor 4. It is not 5 because all detail lives in SKILL.md itself (no one-level-deep reference files for, e.g., the integrations table or extended examples), while it is clearly above 3 since nothing is buried and navigation is easy.

4 / 5

Total

17

/

20

Passed

Description

81%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A highly targeted, trigger-rich description for a narrow Dagster-to-Orchestra migration niche with excellent explicit 'when' guidance and near-zero conflict risk. The main weakness is an under-specified 'what': it never states the concrete mechanism (Orchestra outputs / set_output) the skill applies, and uses a second-person clause ('you need...').

DimensionReasoningScore

Specificity

The description names the domain precisely ('passes data between ops/assets via return values, Out/In wiring, IO managers, or context.add_output_metadata') but states only one actual action — 'that data flow represented in Orchestra' — without naming the mechanism (outputs, set_output). This matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive); it is below 4 because no several specific conversion actions are listed, and the second-person clause 'you need that data flow represented' further weakens capability specificity.

3 / 5

Completeness

Both parts are present: 'when' is explicit and detailed ('Use this skill when... Triggers: any op/asset...'), while 'what' is stated as 'you need that data flow represented in Orchestra'. It fits anchor 4 (both present, one could be more explicit) rather than 5 because the 'what' never says concretely what the skill does (translate to Orchestra's set_output/outputs system); it is clearly above 3 since the 'when' is emphatically explicit.

4 / 5

Trigger Term Quality

Trigger terms are comprehensive and exactly what a user would say when touching this code: 'op/asset that returns a value consumed downstream', 'custom or built-in IOManager', 'Output(value, metadata=...)', 'AssetMaterialization metadata', 'MetadataValue', 'context.add_output_metadata'. This covers class names, API calls, and synonyms (op/asset, custom/built-in), matching the anchor-5 standard of comprehensive natural-term coverage; score 4 would require notable missing variations, and none are evident.

5 / 5

Distinctiveness Conflict Risk

The niche is unambiguous — Dagster data-passing constructs (IOManager, AssetMaterialization, Out/In) migrated to Orchestra — and every trigger term is Dagster-specific, so risk of firing for an unrelated skill is minimal. This matches anchor 5 (clear niche with distinct triggers); anchor 4's 'minor overlap risk with closely related skills' would apply only if generic terms like 'data pipeline' dominated, which they do not.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

15

/

16

Passed

Repository

orchestra-hq/orchestra-skills

Path

skills/migrate-to-orchestra/skills/dagster-io-managers-to-orchestra/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.