菜单
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.
用 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.
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
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.
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-buildkite-jobs |
| description | 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 this as the Buildkite observability base layer.
export BUILDKITE_TOKEN="<token>"
export BUILDKITE_ORG="${BUILDKITE_ORG:-wayve-dot-ai}"
export BUILDKITE_PIPELINE="${BUILDKITE_PIPELINE:-model-ci}"
Fetch one job log to local files:
cd /home/borisindelman/.codex/skills/obs-buildkite-jobs
./scripts/fetch_buildkite_job_log.sh <build_number> <job_id> [output_prefix]
The command prints:
RAW_JSON_PATH=<path>CLEAN_LOG_PATH=<path>BUILDKITE_BUILD_URL=<url>Extract key failure lines from a log:
./scripts/extract_error_lines.sh <clean_log_path> [max_lines=120]