Kestra Agent Skills

A curated collection of agent skills for operating Kestra environments.

Available skills

kestra-flow

Generate, modify, or debug Kestra Flow YAML grounded in the live flow schema — the same way the Kestra AI Copilot does.

Use when:

• Generating a new Kestra flow from a description
• Modifying or extending an existing flow
• Debugging invalid YAML or incorrect task/trigger references

Covers:

• Fetching the live flow schema from https://api.kestra.io/v1/plugins/schemas/flow
• Schema-validated task and trigger generation
• Partial modification (touch only the relevant part)
• Guardrails: no invented types, no hardcoded secrets, correct looping and trigger patterns

Skill path: skills/kestra-flow/SKILL.md

---

kestra-flow-hardening

Audit existing Kestra flows and add production-hardening controls — the consulting counterpart to kestra-flow.

Use when:

• Hardening one or more flows for production
• Auditing flows for resilience, idempotency, and guardrail gaps
• Adding retries, timeouts, error handling, concurrency limits, SLAs, or idempotency guards

Covers:

• Severity-ranked audit report (Critical / High / Medium / Low) with risk, caveat, and proposed fix per finding
• Idempotency judgment — never recommends a blind retry on a non-idempotent write; flags the dedup-guard vs. retry-if-safe branches
• Proportional auditing calibrated by flow signals (triggers, side-effects, namespace env); “already sound” is a valid result
• Surgical, schema-validated edits applied on confirmation, inline and structure-preserving
• Version- and edition-aware (OSS / EE), with EE-only patterns labeled and given an OSS fallback

Skill path: skills/kestra-flow-hardening/SKILL.md

---

kestra-ops

Operate Kestra using kestractl for flow, execution, namespace, and namespace-file operations.

Use when:

• Validating or deploying flows
• Triggering executions and checking status
• Managing namespaces and nsfiles
• Configuring or switching CLI contexts

Covers:

• Context and auth setup (config add, config use, config show)
• Read and inspection flows (flows list/get, executions get, namespaces list)
• Safe write operations (flows deploy, nsfiles upload/delete)
• Operational guardrails for production and automation output

Skill path: skills/kestra-ops/SKILL.md

---

migrate-kestra-2

Guide a full Kestra 1.3 → 2.0 migration: pre-flight audit, server upgrade, CLI-first flow migration, and guided rewrites of the patterns the CLI can’t automate.

Use when:

• Upgrading or migrating an instance to Kestra 2.0
• Checking whether an instance is ready for 2.0 (readiness report + complexity rating)
• Triaging kestra-migrate warnings or flows failing to parse after a 2.0 upgrade

Covers:

• Detect-first audit (probes CLIs, contexts, instance, runs kestra-migrate --check) with a shareable readiness report and Low/Medium/High/Critical complexity tier
• Advisory one-way-door guardrails: verified backup before upgrade (2.0 drops JDBC queue tables irreversibly), accepted risks recorded, never blocked
• CLI-first flow migration with a persistent migration-ledger.md — every flow driven to a terminal state (validated/deployed or deferred-with-reason)
• Guided per-pattern rewrites with diff + confirmation: ForEach/ForEachItem → Loop, trigger conditions → when/dependsOn, pluginDefaults → Policies/inline, removed types
• Server upgrade sequences for Docker Compose and Kubernetes/Helm, EE/OSS branches, kestra migrate plan/run handling
• Composes with kestra-ops and kestra-flow when installed (discovered by skill name — install via npx skills add kestra-io/agent-skills@); standalone kestractl fallback inlined

---

migrate-airflow-kestra

Migrate an Apache Airflow DAG to a production-ready Kestra flow.

Use when:

• Converting an Airflow DAG (.py) to a Kestra flow YAML
• Translating @task-decorated functions or operators into Kestra tasks
• Preserving Airflow parallel execution (fan-out/fan-in) in Kestra

Covers:

• Reading and analysing the Airflow DAG structure, tasks, and dependencies
• Fetching the live Kestra schema from https://api.kestra.io/v1/plugins/schemas/flow
• Extracting Python business logic into namespace files
• Generating schema-validated Kestra flow YAML with correct task ordering and parallelism
• Mapping Airflow XCom data passing to Kestra outputFiles/inputFiles

Skill path: skills/migrate-airflow-kestra/SKILL.md

Usage

Load the skill and provide a concrete operational objective.

Examples:

Use kestra-flow to write a flow that polls a REST API every 30 minutes and stores the result in KV store.

Use kestra-ops to validate and deploy all flows in ./flows to prod.namespace with fail-fast.

Use kestra-ops to run my-flow in my.namespace, wait for completion, and summarize the result.

Use migrate-airflow-kestra to migrate dags/ingest_pipeline.py from Airflow to Kestra, output to kestra/.

Structure

.
├── README.md
└── skills/
    ├── kestra-flow/
    │   └── SKILL.md
    ├── kestra-flow-hardening/
    │   ├── SKILL.md
    │   └── references/
    │       └── hardening-patterns.md
    ├── kestra-ops/
    │   └── SKILL.md
    ├── migrate-airflow-kestra/
    │   └── SKILL.md
    └── migrate-kestra-2/
        ├── SKILL.md
        └── references/
            ├── audit.md
            ├── cli-reference.md
            ├── foreach-to-loop.md
            ├── plugin-defaults.md
            ├── removed-constructs.md
            ├── server-upgrade.md
            └── trigger-conditions.md

Contributing

• Add each skill as skills//SKILL.md.
• Include purpose, trigger conditions, required inputs, workflow, guardrails, and example prompts.
• Keep commands copy-pasteable and production-safe.