Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nvidia/jetson-speculative-decoding
Add EAGLE-3 or draft-model speculative decoding to a Jetson vLLM server when TPOT is the bottleneck.
Passed 18 of 21 test cases with the skill, and 5 of 21 without it.
and 18 more in the full report
14 fixed5 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
What is the recommended handoff workflow after configuring speculative decoding parameters in vLLM on Jetson?
| Checked | Without skill | With skill |
|---|---|---|
| Hands off to jetson-llm-benchmark to quantify speedup results. | Missed | Passed |
The instructions your model reads when the skill loads.
Speculative decoding lets a small "draft" model propose tokens that the target model verifies in a single forward pass, reducing per-token latency. On Jetson, the win/loss is dominated by VRAM headroom, not by the draft quality. This skill encodes the parts an LLM won't already know.
Tune an existing Jetson vLLM deployment for faster token generation by appending the right --speculative-config and validating whether it improves single-stream decode speed.
jetson-inference-mem-tune flags that already pushed --gpu-memory-utilization near the ceiling. Free at least ~2 GB first.jetson-llm-serve.jetson-llm-benchmark before enabling speculation.Append --speculative-config to the vllm serve command shown in jetson-llm-serve.
EAGLE-3 (preferred when a head is published for the target model):
--speculative-config '{
"method": "eagle3",
"model": "<eagle3-head-repo-id>",
"num_speculative_tokens": 5,
"draft_tensor_parallel_size": 1
}'
test cases passed, vs 5 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.