What problem does it solve? Running formal Verl GRPO experiments on remote Ascend NPU servers requires coordinating Docker containers, model and dataset staging, dependency source sync, W&B and Prometheus telemetry, and evidence packaging. This Skill automates that entire pipeline so every run produces reproducible, auditable artifacts. ## Core Features & Use Cases - Formal Case Orchestration: Builds immutable config locks and provenance records, then executes Qwen/geo3k GRPO matrices on remote NPU servers via Docker with reusable container detection. - Asset and Dependency Management: Prepares Qwen3.5 model caches and geometry3k datasets with ModelScope/Hugging Face downloads, resume support, and remote staging, while syncing verl/vllm/transformers/mindspeed source repos with recorded commits. - Telemetry and Evidence Delivery: Streams NPU metrics to Prometheus Pushgateway, names W&B runs semantically, and packages numbered evidence bundles (report, wandb, prometheus, raw logs, config, provenance, rows). - Use Case: Run autoresearch run verl-case to execute a Qwen3.5-2B GRPO training matrix on an A2 server, starting from single-card BS=1 tuning and promoting stable candidates to 8-card throughput cases, then open the generated HTML report with full provenance. ## Quick Start Ask the AI to run a Verl GRPO formal case with Qwen3.5-2B on the geometry3k dataset against a configured NPU server and generate the numbered evidence report.