kestra-flowlisted

# Kestra Flow Skill Use this skill to generate production-ready Kestra Flow YAML grounded in the live schema. ## When to use Use this skill when the request includes: - Generating a new Kestra flow from scratch - Modifying, extending, or debugging an existing flow - Translating a workflow description into valid Kestra YAML ## Required inputs - A description of the desired flow behavior - Namespace (and tenant ID if applicable) - Existing flow YAML if the request is a modification ## Workflow ### Step 1 — Fetch the flow schema Fetch the full schema with `curl` and read it directly — do not pipe it through any interpreter: ```bash curl -s https://api.kestra.io/v1/plugins/schemas/flow ``` Read the raw JSON output to validate every type, property name, and structure used in the output. Do not generate anything before the schema is available. ### Step 2 — Collect context Identify from the user message or conversation: - `id` — flow identifier (preserve if provided) - `namespace` — target namespace (preserve if provided) - Existing flow YAML (for modification requests) - Whether this is an **addition / deletion / modification** or a **full rewrite** ### Step 3 — Generate the YAML Apply all generation rules below, then output raw YAML only. ## Generation rules **Schema compliance** - Use only task types and properties explicitly defined in the fetched schema. Never invent or guess types or property names. - Property keys must be unique within each task or block. **S