kestra-opslisted

# Kestra Operations Skill Use this skill to perform day-to-day Kestra operations with `kestractl`. ## When to use Use this skill when the request includes: - Listing, inspecting, validating, or deploying flows - Triggering executions and checking execution status - Managing namespaces or namespace files (`nsfiles`) - Configuring or switching Kestra CLI contexts ## Required inputs - Target environment or context (`dev`, `staging`, `prod`) - Host URL, tenant, and authentication method (usually token) - Namespace, flow ID, execution ID, and/or local file paths - Output preference (`table` for human-readable, `json` for automation) ## Prerequisites - `kestractl` is installed and executable - Access token and tenant are available - A valid context exists in `~/.kestractl/config.yaml` or values are provided via env vars/flags ## Configuration precedence Resolve config from highest to lowest precedence: 1. Command flags (`--host`, `--tenant`, `--token`, `--output`) 2. Environment variables (`KESTRACTL_HOST`, `KESTRACTL_TENANT`, `KESTRACTL_TOKEN`, `KESTRACTL_OUTPUT`) 3. Config file (`~/.kestractl/config.yaml`) 4. Built-in defaults Common setup: ```bash 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 ``` ## Standard workflow 1. Resolve and confirm the target context. 2. Run read-only discovery first. 3. Validate artifacts befo