tune-ci-thresholds

Calibrate ASR, TTS, and Qwen3-Omni CI thresholds with statistical validation.

768|316|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/sgl-project/sglang-omni --skill tune-ci-thresholds
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tune-ci-thresholds
Source: https://github.com/sgl-project/sglang-omni/tree/main/.claude/skills/tune-ci-thresholds
Command: npx skills add https://github.com/sgl-project/sglang-omni --skill tune-ci-thresholds

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires torch, sglang, uv, and includes scripts (resource) components.

What problem does it solve?

This skill addresses the instability of CI performance and correctness thresholds by providing a statistically sound, automated calibration process that distinguishes between genuine model regressions and transient host-level noise.

Core Features & Use Cases

  • Destructive Round Rejection: Automatically identifies and discards rounds contaminated by host contention or cold caches using robust statistical tests (MAD and gap analysis).
  • Strict Provenance & Readiness: Ensures every calibration run is tied to a specific git commit and environment fingerprint, preventing the use of stale or incompatible data.
  • Use Case: When a new model version causes CI performance tests to flake, use this skill to generate a reliable, worst-of-N threshold report that accounts for hardware variability, ensuring your CI assertions remain stable and meaningful.

Quick Start

Use the tune-ci-thresholds skill to run a full calibration for the omni model on the assigned GPU group and generate a report.

Frequently Asked Questions about tune-ci-thresholds

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I calibrate CI thresholds to distinguish model regressions from host-level noise?

To calibrate CI thresholds and distinguish model regressions from host-level noise, this skill performs repeated, statistically validated observations using MAD and gap analysis to automatically reject destructive rounds contaminated by cold caches or contention.

How do I stabilize flaky CI performance tests across heterogeneous GPU environments?

To stabilize flaky CI performance tests across heterogeneous GPU environments, this skill generates a worst-of-N threshold report that accounts for hardware variability, ensuring your CI assertions remain stable and meaningful.

When do I need statistical validation for CI threshold calibration?

You need statistical validation for CI threshold calibration when a new model version causes CI tests to flake, ensuring that reported metrics represent genuine operational reliability rather than transient host-level noise.

Does CI threshold calibration require strict environment provenance tracking?

Yes, strict environment provenance tracking is required, as this skill ensures every calibration run is tied to a specific git commit and environment fingerprint to prevent the use of stale or incompatible data.

What models are supported for CI threshold calibration with sglang?

CI threshold calibration with sglang currently supports ASR, TTS, and Qwen3-Omni models, validating sample-scope metrics across assigned GPU groups to satisfy operational reliability requirements.

Do I need uv and torch installed to run CI threshold calibration?

Yes, you need uv and torch installed along with sglang, as these dependencies manage the calibration lifecycle, destructive round rejection, and strict sample-scope validation across heterogeneous GPU environments.