CC ci-workflow-guide
Guide to SGLang CI workflow orchestration — stage ordering, fail-fast, gating, partitioning, execution modes, and debugging CI failures. Use when modifying CI workflows, adding stages, debugging CI pipeline issues, or understanding how tests are dispatched and gated across stages.
Guide to SGLang CI workflow orchestration — stage ordering, fail-fast, gating, partitioning, execution modes, and debugging CI failures.
As a process C 52/100 · Has gaps — References files that are not bundled: ../write-sglang-test/SKILL.md, scripts/ci/opt_in_ci_tiers.json, scripts/ci/utils/slash_command_handler.py
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 6722 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: ../write-sglang-test/SKILL.md - warning
missing-refreference to a missing file: scripts/ci/opt_in_ci_tiers.json - warning
missing-refreference to a missing file: scripts/ci/utils/slash_command_handler.py - warning
missing-refreference to a missing file: scripts/ci/runner_configs.yml - warning
missing-refreference to a missing file: scripts/lint/check_opt_in_ci_tiers.py - note
edit-residuethe text marks something as outdated (lines 440, 451): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 52/100
- 0Tools and files. 5 referenced file(s) missing: ../write-sglang-test/SKILL.md, scripts/ci/opt_in_ci_tiers.json, scripts/ci/utils/slash_command_handler.py
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 6722 tokens
- 100Steps. 38 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- low 14 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (26 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 281: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 38 items
- +3Output format is stated explicitly
- +4Has examples (7 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.