skills/kestra-ops/SKILL.md
Operate Kestra environments using kestractl for context setup, flow inspection, flow validation and deployment, execution monitoring, namespace operations, and namespace file management. Use when users request Kestra operational CLI tasks in dev, staging, or production.
npx skillsauth add kestra-io/agent-skills kestra-opsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill to perform day-to-day Kestra operations with kestractl.
Use this skill when the request includes:
nsfiles)dev, staging, prod)table for human-readable, json for automation)kestractl is installed and executable~/.kestractl/config.yaml or values are provided via env vars/flagsResolve config from highest to lowest precedence:
--host, --tenant, --token, --output)KESTRACTL_HOST, KESTRACTL_TENANT, KESTRACTL_TOKEN, KESTRACTL_OUTPUT)~/.kestractl/config.yaml)Common setup:
kestractl config add dev http://localhost:8080 main --token DEV_TOKEN
kestractl config add prod https://prod.kestra.io production --token PROD_TOKEN
kestractl config use dev
kestractl config show
--wait for run operations where needed).Flows:
kestractl flows list my.namespace
kestractl flows get my.namespace my-flow
kestractl flows validate ./flows/
kestractl flows deploy ./flows/ --namespace prod.namespace --override --fail-fast
Executions:
kestractl executions run my.namespace my-flow --wait
kestractl executions get 2TLGqHrXC9k8BczKJe5djX
Namespaces:
kestractl namespaces list
kestractl namespaces list --query my.namespace
Namespace files:
kestractl nsfiles list my.namespace --path workflows/ --recursive
kestractl nsfiles get my.namespace workflows/example.yaml --revision 3
kestractl nsfiles upload my.namespace ./assets resources --override --fail-fast
kestractl nsfiles delete my.namespace workflows --recursive
deploy, upload, delete).flows validate before flows deploy.--output json for scripting and automation reliability.--verbose in shared logs because it can expose credentials.nsfiles actions, confirm path scope and only use --force intentionally.kestra-ops to validate and deploy all flows in ./flows to prod.namespace with fail-fast enabled, then report what changed."kestra-ops to run my-flow in my.namespace, wait for completion, and summarize execution status."kestra-ops to upload ./assets to namespace files under resources with override enabled, then list uploaded files recursively."development
Migrate an Airflow DAG to a production-ready Kestra flow. Extracts Python task logic into namespace files, maps DAG dependencies to Kestra tasks, and preserves parallel execution structure.
development
Generate, modify, or debug Kestra Flow YAML by fetching the live flow schema and applying the same guardrails used by the Kestra AI Copilot. Use when users ask to create, write, update, or fix a Kestra flow.
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------