Individual skill
ray-llm
LLM workloads on open-source Ray (pinned to 2.57) — OpenAI-compatible serving with ray.serve.llm (vLLM-backed LLMConfig + build_openai_app) and batch inference with ray.data.llm (build_processor). Corrects the stale defaults a model produces — the archived ray-llm repo and its YAML configs, hand-rolled vLLM engines inside plain Serve deployments, the removed build_llm_processor name, deprecated boolean stage flags, top-level LLMServer/LLMRouter imports, free-form accelerator strings, one-deployment-per-LoRA-adapter designs — with the 2.57 idioms (stage configs, placement_group_config over hand-rolled PGs, deployment_config autoscaling, dynamic LoRA multiplexing, prefix-cache-affinity routing, the full OpenAI endpoint surface). Use when writing, reviewing, or productionizing LLM serving or batch inference on Ray. Classic-ML Ray (Train/Tune/Data/Serve/clusters) lives in the sibling ray skill.
skills/.experimental/ray-llm/SKILL.md
Source commit cf93c57cac89d6fc3e4194686000411567f5caf3
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 222
- Repository last updated
- Aug 15, 2026
- License
- MIT
Observed agent integration: codex
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
AGENTS.mddoc · 5,311 bytesSKILL.mdcore · 6,879 bytesSKILL.mdcore · 6,879 bytesSKILL.mdcore · 6,879 bytesSKILL.mdcore · 6,879 bytesassets/templates/_template.mddoc · 1,129 bytesmetadata.jsonasset · 2,132 bytesreferences/_sections.mddoc · 2,711 bytesreferences/api-endpoint-surface-cpu-validation.mddoc · 1,669 bytesreferences/api-lora-dynamic-multiplexing.mddoc · 1,222 bytesreferences/batch-build-processor-renamed.mddoc · 1,470 bytesreferences/batch-concurrency-and-alternatives.mddoc · 1,359 bytesreferences/batch-stage-configs-not-flags.mddoc · 1,660 bytesreferences/place-accelerator-type-validated.mddoc · 1,353 bytesreferences/place-engine-builds-pg.mddoc · 1,796 bytesreferences/scale-autoscaling-deployment-config.mddoc · 1,505 bytesreferences/scale-prefix-cache-routing.mddoc · 1,435 bytesreferences/serve-builtin-not-handrolled.mddoc · 1,471 bytesreferences/serve-deprecated-server-router.mddoc · 1,391 bytesreferences/serve-model-id-vs-source.mddoc · 1,283 bytesreferences/serve-ray-llm-extra-pins-vllm.mddoc · 988 bytes
Read excerpt
# Ray LLM
Library-reference skill for LLM workloads on open-source Ray — 13 rules across 5 categories covering `ray.serve.llm` (OpenAI-compatible, vLLM-backed serving) and `ray.data.llm` (batch inference). This surface churned faster than any other part of Ray — a standalone repo was absorbed and archived, entry points were renamed, and config shapes restructured — so the examples a model learned from mostly no longer run. Each rule names the wrong default it corrects; there is no rule for things a capable model already gets right.
Scope is the LLM-specific layer. Generic Serve/Data/cluster decisions (deployment lifecycle, autoscaling semantics, KubeRay) are the sibling [`ray`](../ray/) skill — the two compose.
Pinned to **ray 2.57.0** (`ray[llm]` extra, which pins its matching vLLM). API claims were verified against the unpacked 2.57.0 wheel and the installed package source, and every config example in the rules was constructed under CPU-only pydantic validation (including the traps, which fail exactly as described); engine/GPU runtime behavior is source-verified only — no model was actually served.
## When to Apply
- Standing up or reviewing an OpenAI-compatible LLM serving deployment on Ray
- Writing batch LLM inference over datasets — summarization, embedding, scoring at scale
- Sizing or placing multi-GPU models — tensor/pipeline parallelism, accelerator selection
- Scaling LLM deployments — replica autoscaling, ingress sizing, request routing