sglang-model-day0-support

Plans and audits evidence-driven SGLang Day-0 support programs for new model architectures.

783|67|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/BBuf/AI-Infra-Auto-Driven-SKILLS --skill sglang-model-day0-support
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sglang-model-day0-support
Source: https://github.com/BBuf/AI-Infra-Auto-Driven-SKILLS/tree/main/skills/model-optimization/sglang-model-day0-support
Command: npx skills add https://github.com/BBuf/AI-Infra-Auto-Driven-SKILLS --skill sglang-model-day0-support

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Shipping Day-0 support for a new LLM, VLM, MoE, or speculative-decoding model in SGLang involves far more than registering a model class: teams must lock immutable revisions, map architecture gaps, split work into reviewable PRs, validate seven correctness gates, and sanitize private evidence before publishing. This Skill turns that ad-hoc effort into an auditable, repeatable program.

Core Features & Use Cases

  • Eight-file Day-0 bundle: Generates and validates a scope contract, architecture gap map, PR DAG, validation matrix, release lock, PR body, follow-up ledger, and sanitization report.
  • Evidence discipline: Enforces machine-checkable public PR evidence records with immutable heads, states, and limitations, plus a validation hierarchy that prevents upgrading unit tests into end-to-end claims.
  • Case-study guidance: Ships manually reviewed Kimi K3 and DeepSeek V4 public case studies covering hybrid attention, speculative state, quantization, platform ports, and revert handling.
  • Use Case: When a new model like a hybrid KDA/MLA VLM is announced, use this Skill to produce the full support plan, classify each patch as day0-required versus performance-only, and validate the final public PR bundle with the included scripts.

Quick Start

Use the sglang-model-day0-support skill to design and validate an auditable SGLang Day-0 support bundle for this model.

Frequently Asked Questions about sglang-model-day0-support

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

FAQPage Schema
How do I plan Day-0 support for a new model in SGLang?

Start by filling the scope contract and release lock with immutable model, tokenizer, and SGLang revisions, then build an architecture gap map against the locked SGLang source. The Skill guides you through a PR DAG, validation matrix, and seven gates before writing the public PR body.

What files does an SGLang Day-0 support bundle require?

The bundle requires eight files: scope-contract.md, architecture-gap-map.md, pr-dag.md, validation-matrix.md, release-lock.md, pr-body.md, follow-up-ledger.md, and sanitization-report.md. The validate_day0_bundle.py script checks all required headings, placeholders, and evidence records.

How are Day-0 requirements distinguished from later optimizations?

Every work item is classified as day0-required, post-day0-fix, performance-only, or experiment-or-revert. Only items needed to load, serve, produce correct API output, or satisfy an announced release lane count as Day-0; kernels with correct fallbacks are typically performance-only.

Can I use private development history in the public support PR?

No. The sanitization policy forbids private repository identifiers, machine names, internal benchmark IDs, and non-public artifact references. Private lessons must be re-derived from public sgl-project/sglang evidence, and an uncommitted denylist scan runs before publication.

Does server startup prove a model is correctly supported?

No. Startup is evidence only for the load gate. Output correctness, state correctness, topology composition, and performance each require their own gate evidence, such as deterministic generation, cache lifecycle tests, and named-hardware benchmarks.