Agent skill · AI & Agents

jetson-inference-mem-tune

Pick the serving stack and per-runtime memory flags (vLLM, SGLang, llama.cpp, TensorRT Edge-LLM) for an LLM/VLM workload on any NVIDIA Jetson.

NVIDIAgithub.com/NVIDIAGitHub ↗
claude-codecodexships scriptsApache-2.0
Install
npx skills add NVIDIA/skills --skill jetson-inference-mem-tune --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 6
SKILL.md size: 11 KB
Bundled scripts: yes
Version: 0.0.1
Declared author: Jetson Team
Path: skills/jetson-inference-mem-tune/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,789
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Jetson Inference Memory Tuning Recommends an inference runtime and the specific memory-related flags to pass to it, given the Jetson SKU/variant and the user's workload. Does not include quantization recipe selection — that lives in the model-benchmarking skill — but it does point at the precision floor each runtime can serve efficiently. ## Purpose Turn a live `jetson-memory-audit` snapshot int

More from skills
All skills →
About this skill
What does the jetson-inference-mem-tune skill do?

Pick the serving stack and per-runtime memory flags (vLLM, SGLang, llama.cpp, TensorRT Edge-LLM) for an LLM/VLM workload on any NVIDIA Jetson.

How do I install it?

Run `npx skills add NVIDIA/skills --skill jetson-inference-mem-tune --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From NVIDIA/skills, a repository with 2,789 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going