voyager-launchlisted

Complete one-shot Voyager SDK launcher for Axelera AI Metis pipelines and demos. Use when the user asks to build, create, launch, run, verify, package, open a browser result viewer, or show results for a complete AI vision pipeline from a natural-language request (including when they want to debug or evaluate a pipeline you are building end-to-end), covering detection, tracking, pose, face, segmentation, depth estimation, video, USB camera, RTSP, app/demo, or output-video workflows. Prefer this over voyager-new-pipeline, voyager-run, voyager-deploy, voyager-bench, and voyager-new-app whenever the user wants an autonomous end-to-end runnable solution with RUN_HERE.sh, Metis execution, validation artifacts, logs, browser viewer, and evaluation output.
fxd0h/Axelera-Voyager-Local-Assistant · ★ 4 · AI & Automation · score 75

Install: claude install-skill fxd0h/Axelera-Voyager-Local-Assistant

# Launch - Complete Pipeline Builder Build a complete runnable Voyager SDK solution from the user prompt. Optimize for speed, but never trade away validation integrity. ## Use This Skill When / Not When - Use when: the user wants a complete runnable pipeline or demo from natural language, with validation artifacts and a browser viewer. - Not when: the model/pipeline already exists and they only want to execute it -- route to voyager-run. - Not when: they explicitly want YAML-only design -- route to voyager-new-pipeline. - Not when: they bring an existing error or log to fix in existing code -- route to voyager-debug. {{INCLUDE workflows/pre-flight.md}} ## Launch Contract A launch is complete only when it creates a runnable package and one of these outcomes is true: - On a Metis machine: `RUN_HERE.sh` ran successfully on Metis, not CPU, and produced `VALIDATED.txt`, `results/EVALUATION.json`, `results/METIS_PROOF.json`, `results/RUN_SUMMARY.json`, `results/VIEWER_CHECKS.json`, a log, an output image/video, and an Open Design-style Axelera dark/gold browser viewer at `viewer/index.html` that is auto-opened by default. `results/METIS_PROOF.json` must have `status=passed`, `metis_detected=true`, `accelerator_operator_seen=true`, `cpu_only_rejected=true`, and metrics schema `voyager.metrics.v1` with measured end-to-end FPS, measured Metis device FPS from the SDK tracer, measured SDK latency, stage metrics, slowest SDK stage evidence, `metric_truth_gates`, `metric_boun