skills.rest
sgl-project
sgl-projectOFFICIAL
Explore all skills by this author →
GitHub

cookbook-migrate-model

Migrate legacy SGLang cookbook pages to the config-driven template format.

33.0k|8.4k|Updated Jan 8, 2024
Search Tags:#config-driven#mdx#Documentation#SGLang#cookbook#Mintlify#Migration
One-click install
npx skills add https://github.com/sgl-project/sglang --skill cookbook-migrate-model
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cookbook-migrate-model
Source: https://github.com/sgl-project/sglang/tree/main/.claude/skills/cookbook-migrate-model
Command: npx skills add https://github.com/sgl-project/sglang --skill cookbook-migrate-model

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

SGLang's documentation contains legacy per-model cookbook pages built as monolithic JSX generators that must be converted to a shared config-driven template (shared _deployment.jsx / _playground.jsx engines plus per-model config) without losing any measured benchmark data, flags, or hardware support matrices.

Core Features & Use Cases

  • Faithful legacy-to-config transcription: Converts legacy generator option spaces into the 5-dimension matrix (hardware, variant, quantization, strategy, nodes) with strict rules against modernizing flags, versions, or docker tags.
  • Verified benchmark policy: Migrates only measured results anchored to reproducible versions (release tags, commits, or day-0 PRs), dropping non-reproducible numbers while keeping reproduce commands.
  • Token-level equivalence audit: Requires an independent audit that diffs the original generator's output against the new cells token-by-token, plus Mintlify validation and browser smoke checks.
  • Use Case: Run with a model page name like GLM-5.1 to produce one migration PR containing the new config, benchmarks file, rewritten MDX, and the deleted legacy generator.

Quick Start

Migrate the legacy GLM-5.1 cookbook page to the config-driven template and open one PR with the audit results.

Frequently Asked Questions about cookbook-migrate-model

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

FAQPage Schema
How do I migrate a legacy SGLang cookbook page to the config-driven template?▼

Run the skill with the model page name, e.g. /cookbook-migrate-model GLM-5.1. It inventories the legacy generator and MDX, maps controls to the 5-dimension matrix, generates the config with a token-level audit, and produces one PR per model.

What is the difference between cookbook-migrate-model and cookbook-add-model?▼

cookbook-migrate-model converts existing legacy pages to the config-driven format, treating the legacy page as the single source of truth. cookbook-add-model is for brand-new model pages, and the migration skill reuses its templates and authoring references.

When are benchmark numbers kept during a cookbook migration?▼

Benchmark results migrate only when the sglang_version is a reproducible anchor: a release tag, commit hash, or a specific day-0 PR. Results measured against moving refs like the main branch are dropped entirely, while benchmarkCommands are kept for re-measurement.

Can the migration change engine files like _deployment.jsx or _playground.jsx?▼

No, engines are read-only in a migration PR. Model-specific features must be expressed as config data consumed by generic axis handlers such as flagSelects; only a genuinely new control shape would need a separate prior engine PR.

Why are parser flags like --reasoning-parser never baked into deployment cells?▼

Parser flags are a Playground-only feature by convention. Deployment cells always ship without them, and the parsers axis adds them on top as green additions, keeping deployment commands faithful to the measured baseline.

How is the migration verified for correctness?▼

An independent audit extracts the original generator via git show main:<path>, stubs React hooks, runs every combo, and token-diffs against the new cells. The PR also requires mint validate, mint broken-links, and a browser smoke test.

Related Skills

Explore More Software Engineering Skills→
fwdslshfwdslsh
2

doc-writer

Generate and improve Markdown documentation for JavaScript projects.

Official
Basic
kiloloopkiloloop

review-loop-author

Automate code review feedback on GitHub Pull Requests with multi-round iterations.

Official
Advanced
tagtytagty

code-patterns

Reference Taskflow code patterns for database queries, Server Actions, and Server Components.

Community
Basic
aslaiiaslaii

gsd-fast

Execute trivial tasks directly without spawning subagents or creating PLAN.md files.

Community
Basic