CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

prefect-conditions-to-orchestra

Use this skill when a Prefect flow contains conditional execution logic: tasks that only run based on the result of upstream tasks, if/else branches driven by task return values, allow_failure=True patterns, or conditional .submit() calls. Triggers: any Prefect flow with if/else branching on task outputs, any task called conditionally, any use of Prefect states to control downstream execution.

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/migrate-to-orchestra/skills/prefect-conditions-to-orchestra/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

The body is highly actionable with exact syntax, complete YAML, and a concrete before/after example, and its conversion checklist is clearly sequenced. Its main weaknesses are token duplication — the same ~40-line YAML pipeline appears twice nearly verbatim — and the lack of a final validation checkpoint. Cross-skill navigation to sibling skills and external docs is clearly signaled.

Suggestions

Delete one of the two near-identical YAML pipeline blocks — either keep the Before/After example (which shows both sides) and drop the 'Orchestra YAML Structure' section, or keep the structure section and trim the After example to only the changed fields.

Mention allow_failure=True → treat_failure_as_warning once (in the mapping table) and remove its repetition in both the Conversion Steps and the Gotchas list.

Add a final checklist step to verify generated conditions reference real task IDs and output keys, e.g., 'Confirm every condition's PIPELINE_RUN_TASKS task-id exists and its OUTPUTS key is set by an upstream set_outputs: true task'.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows and uses tight table/gotcha formats, but the 'Orchestra YAML Structure' example and the 'After' half of the Before/After example are near-identical ~40-line YAML blocks (only the pipeline name differs), and allow_failure guidance appears in the mapping table, the conversion steps, and the gotchas. The duplication is more than minor trimming, keeping it below anchor 4 but well above anchor 2's padded-prose verbosity.

3 / 5

Actionability

Fully executable guidance throughout: exact Orchestra field names, complete copy-paste-ready YAML pipelines, exact condition syntax ("${{ ORCHESTRA.PIPELINE_RUN_TASKS['task-check-new-data'].OUTPUTS['row_count'] > 0 }}"), and a concrete before/after pair covering the most common case. Deferrals (set_output client setup, matrix) are explicitly routed to a named sibling skill.

5 / 5

Workflow Clarity

The Conversion Steps checklist is a clear, well-ordered sequence (identify branches, classify input-driven vs output-driven, write conditions, replace allow_failure/wait_for, flag .map()), and the classification step acts as an implicit checkpoint. The conversion is neither destructive nor batch, so no cap applies; the gap is the absence of any final validation step (e.g., verify conditions reference real task outputs), which is a minor rather than structural gap.

4 / 5

Progressive Disclosure

Well-organized single-file skill with clear sections (mapping table, structure, steps, example, gotchas) and well-signaled one-level references: named sibling skills ('See prefect-data-passing-to-orchestra', 'See prefect-alerts-to-orchestra') and external doc links. No bundle files exist to split content into, but at ~165 lines the duplicated full YAML examples are inline content that better organization would consolidate, so it does not reach anchor 5.

4 / 5

Total

16

/

20

Passed

Description

61%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.

The description excels at explicit, concrete trigger guidance but completely omits what the skill does — a user reading only the description cannot learn that it converts Prefect conditionals into Orchestra condition expressions. It also states its triggers twice with near-identical wording. Strong on when, silent on what.

Suggestions

State the capability up front, e.g. 'Converts Prefect conditional execution patterns (if/else on task outputs, allow_failure=True, conditional .submit()) into Orchestra condition: expressions.'

Remove the redundant 'Triggers:' sentence that restates the first sentence's conditions nearly verbatim, and use the freed space for the missing what-statement.

Add a few natural trigger variants users might say, such as 'tasks that only run when a previous task succeeds' or 'conditional logic in Prefect flows'.

DimensionReasoningScore

Specificity

The description names its domain and lists concrete trigger patterns ('if/else branches driven by task return values, allow_failure=True patterns, or conditional .submit() calls'), but it never states any action the skill performs — the conversion to Orchestra condition expressions appears nowhere, so it does not reach anchor 4's 'lists several specific actions'. It is not anchor 2 because the language is concrete rather than generic.

3 / 5

Completeness

The 'when' is explicitly and richly answered ('Use this skill when a Prefect flow contains conditional execution logic... Triggers: any Prefect flow with if/else branching on task outputs'), but the 'what' — what the skill actually does — is entirely absent. This falls between anchor 2 ('only when present without what') and anchor 3; the exceptional when-quality pulls it to 3, but the missing what prevents anything higher.

3 / 5

Trigger Term Quality

Natural terms a Prefect user would say are well covered: 'if/else branching on task outputs', 'task called conditionally', 'Prefect states', 'downstream execution', 'conditional .submit() calls'. A few plausible variations (e.g., 'run tasks only if', 'skip tasks', 'conditional logic') are missing, keeping it below the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche (Prefect conditional execution) with distinctive terms like 'allow_failure=True patterns' and 'Prefect states'. Minor overlap risk exists with the closely related sibling skill prefect-data-passing-to-orchestra, since 'conditional .submit() calls' brushes against that skill's data-passing territory.

4 / 5

Total

14

/

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: 4 missing

Warning

Total

15

/

16

Passed

Repository

orchestra-hq/orchestra-skills

Path

skills/migrate-to-orchestra/skills/prefect-conditions-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.