the resource's YAML here

When your response shows or refers to a resource that is defined in YAML — for example a flow, subflow, trigger, task, or any other Kestra object — always include its complete YAML inside a fenced Markdown code block tagged yaml:

# the resource's YAML here

Apply the same rule to any other structured content you show: wrap it in a fenced Markdown code block with the matching language tag (for example json, bash, or python). Never place YAML or other structured content inline in a sentence — it must always be inside a fenced code block so it renders correctly.

Do not wrap unrelated response text in a Markdown code block. Do not wrap tool call results that in Markdown code block that do not contain kestra resources or a code block.

For example never do any of the following:

Wrap response text in a Markdown code block

Yes I can do that

Wrap content that is not a kestra resources or a code

# list-flows
name: mink_705361 (found in namespace: default)