What is prefect-flow-structure-to-orchestra?

A conversion guide for moving Prefect workflows—Python programs that run scheduled data or automation tasks—into Orchestra YAML, a configuration format for Orchestra pipelines.

Use it when converting Prefect flow-level configuration into Orchestra pipeline settings.

It prevents flow settings such as schedules, retries, timeouts, inputs, and deployments from being copied into the new format incorrectly.

prefect-flow-structure-to-orchestra — Skill for Claude Code by orchest

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add orchestra-hq/orchestra-skills --skill prefect-flow-structure-to-orchestra

Clone the repo

git clone --depth 1 https://github.com/orchestra-hq/orchestra-skills

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/prefect-flow-structure-to-orchestra/github.svg)](https://agentmods.dev/skills/orchestra-hq/orchestra-skills/prefect-flow-structure-to-orchestra)

Your own site

<a href="https://agentmods.dev/skills/orchestra-hq/orchestra-skills/prefect-flow-structure-to-orchestra"><img src="https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/prefect-flow-structure-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/orchestra-hq/orchestra-skills/prefect-flow-structure-to-orchestra"><img src="https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/prefect-flow-structure-to-orchestra.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 102 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,634 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.

Model	Per session	Once invoked
Fable 5.1	$0.00102	$0.01634
Opus 5	$0.00051	$0.00817
Sonnet 5	$0.00020	$0.00327
Haiku 4.5	$0.00010	$0.00163

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

Security

Grade A, and why

prefect-flow-structure-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-flow-structure-to-orchestra/SKILL.md · 125 lines

How it starts

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

Overview

This skill handles conversion of Prefect @flow-level constructs into Orchestra pipeline root fields. Apply it first, before converting individual tasks. It covers scheduling, retries, timeouts, typed parameters, tags, concurrency, and deployment config.

Parameter Mapping

Prefect construct	Orchestra field	Notes
`@flow(name="my-flow")`	`name: my-flow`	kebab-case recommended
`CronSchedule(cron="0 2 * * *", timezone="UTC")`	`schedule: [{cron: "0 2 * * ? *", timezone: UTC}]`	Prefect's cron is standard 5-field — convert to Orchestra's 6-field AWS EventBridge cron, do NOT copy verbatim
`IntervalSchedule(interval=timedelta(hours=6))`	`schedule: [{cron: "0 /6 * ? *"}]`	Non-clean intervals → MANUAL note
`RRuleSchedule(...)`	MANUAL note	No rrule support in Orchestra
`def my_flow(env: str = "prod")`	`inputs: {env: {type: string, default: prod}}`	int/float→number, str→string, bool→boolean
`@flow(retries=2, retry_delay_seconds=300)`	`configuration: {retries: 2, retry_delay: 5}`	Orchestra's `retry_delay` is MINUTES — convert seconds/60 (round up); cap at 120 — clamp and flag if larger
`@flow(timeout_seconds=3600)`	`configuration: {timeout: 3600}`
tag-based concurrency limit	`configuration: {concurrency: {max_active: 1}}`	+ MANUAL note
`@flow(log_prints=True)`	drop	No equivalent; omit
`@flow(tags=["elt"])`	`tags: [elt]` on each task individually (NOT on the group — `TaskGroupModel` has no `tags` field)
`SecretStr` params	→ `prefect-secrets-to-orchestra`	never inline

Orchestra YAML Structure

version: v1
name: nightly-elt
schedule:
  - cron: '0 2 * * ? *'
    timezone: UTC
configuration:
  retries: 2
  retry_delay: 5
  timeout: 3600
inputs:
  target_env:
    type: string
    default: prod
  row_limit:
    type: number
    default: 0
    optional: true
pipeline:
  # ... tasks with tags: [elt]

Conversion Steps

Extract @flow(name=...) → name: (kebab-case)
Extract schedule from .serve() or .deploy() call → schedule: array
Map CronSchedule → convert 5-field cron to Orchestra's 6-field AWS EventBridge cron + timezone; IntervalSchedule → approximate cron or MANUAL note; RRuleSchedule → MANUAL note
Extract typed function params → inputs: (str→string, int/float→number, bool→boolean, dict→dict, list→list)
Map retries=, retry_delay_seconds= → configuration.retries, configuration.retry_delay (convert seconds to minutes)
Map timeout_seconds= → configuration.timeout
Map tags= → propagate to each task's tags: field
Drop log_prints, persist_result, result_storage (no Orchestra equivalent)
Flag SecretStr params for prefect-secrets-to-orchestra
Flag on_failure/on_completion hooks for prefect-alerts-to-orchestra

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

12d ago First seen · 125 lines · 102 tokens per session scan A 60ee3e239ec4

Subscribe to this mod's changes

prefect-flow-structure-to-orchestra is a skill published in the GitHub repository orchestra-hq/orchestra-skills (9 stars, last pushed 3d ago), licensed MIT. It adds 102 tokens to every session and 1,634 once invoked, about $0.0005 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.

DevOps and cloud

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