メニュー
Inspect Flyte execution status and per-node/per-task log URIs from a Flyte Console execution URL. Use when a user asks for workflow status, step status, or logs for flyte.data.wayve.ai/dev executions.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
End-to-end run-image classification with Gemini, including image fetch, prompt control, and JSON output. Use when you need parking or pull-over labels from a run_id.
Find a Gen2 MCAP from a run (or model-derived run), list topics, and extract topic/field values at a specific log time. Use when debugging run-level protobuf signals such as controller_state.
Fetch Buildkite job logs and extract failure lines for debugging CI jobs. Use when a user provides build/job ids or requests failure signal from Buildkite.
Use when forming Spark/SQL queries for Databricks parking evaluation - provides table schemas, PySpark patterns, joins, and filter patterns for PUDO/UNPUDO analysis
Work with Databricks notebooks using the REST API - list, read, modify, and write notebooks back to Databricks workspace
Shared Model Catalogue primitives (resolve model refs, find latest checkpoint, call API helpers) used by model lookup/summary/checkpoint/modelci skills. Use when model references must be normalized before downstream analysis.
| name | obs-flyte-execution |
| description | Inspect Flyte execution status and per-node/per-task log URIs from a Flyte Console execution URL. Use when a user asks for workflow status, step status, or logs for flyte.data.wayve.ai/dev executions. |
Use this skill as the Flyte observability base layer.
Install runtime Bazel files into WayveCode/.ai/skills first:
cd /home/borisindelman/.codex/skills/obs-flyte-execution
./install.sh
Then run:
./scripts/inspect_flyte_execution.sh "<flyte_execution_url>" --json
Human-readable output:
./scripts/inspect_flyte_execution.sh "<flyte_execution_url>"
This skill stores the Bazel runtime files in ~/.codex/skills/obs-flyte-execution/:
BUILDinspect_execution_logs_cli.pyinstall.sh copies those two files to:
/workspace/WayveCode/.ai/skills/obs-flyte-execution/so Bazel can run:
bazel run //.ai/skills/obs-flyte-execution:inspect_execution_logs_cli -- "<flyte_execution_url>"
flyte.data.wayve.ai and flyte.data.wayve.dev console URLs../install.sh whenever you change BUILD or inspect_execution_logs_cli.py in this skill.Optional custom destination for install.sh:
./install.sh /workspace/WayveCode/.ai/skills