prefect-conditions-to-orchestra

prefect-conditions-to-orchestra is a skill for Claude Code from orchestra-hq/orchestra-skills. It costs 88 tokens per session (1,427 once invoked), scanned A, original, MIT.

A conversion guide for replacing conditional logic in Prefect workflows with conditions in Orchestra pipelines. It covers branches based on inputs or earlier task results, failed tasks treated as warnings, dependencies, and mapped tasks.

In plain words
What is it for?
Use it when migrating Prefect flows with `if/else` branches, conditional task submission, `allow_failure`, always-run tasks, or dependencies without data passing.
Why use it?
Prefect expresses decisions in Python, while Orchestra expresses them with pipeline condition fields and output references. The guide shows how to preserve when tasks run, skip, or continue after a warning.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is command: python scripts/process_records.py.

Part of the migrate-to-orchestra plugin — 52 skills shipped together

Good fit Use it when migrating Prefect flows with if/else branches, conditional task submission, allow_failure, always-run tasks, or dependencies without data passing.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/orchestra-hq/orchestra-skills
agentmods
npx agentmods add skills/orchestra-hq/orchestra-skills/prefect-conditions-to-orchestra

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.

agentmods badge for prefect-conditions-to-orchestra

README.md
[![agentmods](https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/prefect-conditions-to-orchestra/github.svg)](https://agentmods.dev/skills/orchestra-hq/orchestra-skills/prefect-conditions-to-orchestra)
Your own site
<a href="https://agentmods.dev/skills/orchestra-hq/orchestra-skills/prefect-conditions-to-orchestra"><img src="https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/prefect-conditions-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.

agentmods 80×15 button for prefect-conditions-to-orchestra

Your own site · 80×15
<a href="https://agentmods.dev/skills/orchestra-hq/orchestra-skills/prefect-conditions-to-orchestra"><img src="https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/prefect-conditions-to-orchestra.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 88 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,427 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00088 $0.01427
Opus 5 $0.00044 $0.00714
Sonnet 5 $0.00018 $0.00285
Haiku 4.5 $0.00009 $0.00143

Measured 12d ago against content hash 46cb5bde14d2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

prefect-conditions-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 12d 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/prefect-conditions-to-orchestra/SKILL.md · 169 lines

How it starts

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

Overview

This skill converts Prefect conditional execution patterns into Orchestra condition: expressions. It covers input-driven branches, runtime output-driven branches, allow_failure patterns, and always-run tasks.

Parameter Mapping

Prefect construct Orchestra field Notes
Default (no condition) condition: null Orchestra default
Input-driven branch condition: "${{ inputs.flag == true }}" Decision known at trigger time
result = task.submit(); if result.result(): upstream PYTHON task with set_outputs: true + downstream condition Runtime decision via outputs
allow_failure=True treat_failure_as_warning: true on upstream task Downstream continues regardless
Skip if no data condition: "${{ ORCHESTRA.PIPELINE_RUN_TASKS['id'].OUTPUTS['key'] > 0 }}"
Always run condition: "${{ True }}" Runs even if upstream failed
.submit(wait_for=[other]) depends_on: [other-task-id] Dependency without data passing
.map() over list matrix: block on TaskGroupModel See prefect-data-passing-to-orchestra

Orchestra YAML Structure

version: v1
name: conditional-pipeline
pipeline:
  stage-check:
    tasks:
      task-check-new-data:
        integration: SNOWFLAKE
        integration_job: SNOWFLAKE_RUN_QUERY
        parameters:
          statement: "SELECT COUNT(*) AS row_count FROM staging.new_records"
        depends_on: []
        condition: null
        tags: []
    depends_on: []

  stage-process:
    tasks:
      task-process-records:
        integration: PYTHON
        integration_job: PYTHON_EXECUTE_SCRIPT
        parameters:
          command: python scripts/process_records.py
        depends_on: []
        condition: "${{ ORCHESTRA.PIPELINE_RUN_TASKS['task-check-new-data'].OUTPUTS['row_count'] > 0 }}"
        tags: []
    depends_on:
      - stage-check

  stage-skip:
    tasks:
      task-log-skip:
        integration: PYTHON
        integration_job: PYTHON_EXECUTE_SCRIPT
        parameters:
          command: python scripts/log_skip.py
        depends_on: []
        condition: "${{ ORCHESTRA.PIPELINE_RUN_TASKS['task-check-new-data'].OUTPUTS['row_count'] == 0 }}"
        tags: []
    depends_on:
      - stage-check

Read the full file on GitHub · 169 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.

  1. 12d ago First seen · 169 lines · 88 tokens per session scan A 46cb5bde14d2

Subscribe to this mod's changes

prefect-conditions-to-orchestra is a skill published in the GitHub repository orchestra-hq/orchestra-skills (9 stars, last pushed 3d ago), licensed MIT. It adds 88 tokens to every session and 1,427 once invoked, about $0.0004 per session on Opus 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens