dgx-station-mig
Skill1.5k starsChanged 2 months agoApache-2.0View on GitHub
Inspect NVIDIA DGX Station GB300 MIG state and installed-driver profiles, create a digest-bound layout plan, disclose disruption and restoration, and apply an approved still-valid plan. Use when the user asks to enable, disable, partition, reconfigure, inspect, or troubleshoot MIG instances or needs MIG UUIDs. Never assume static profile IDs or terminate GPU clients.
Trending
More talk lately.about the whole repository
Who's talking about NVIDIA/dgx-spark-playbooks
- CarstVaartjes/vonk-forge-recipes“Refresh needs review: gemma-4-e4b-it-nvidia-vllm-single”GitHub · Nov 3, 2026
- CarstVaartjes/vonk-forge-recipes“Refresh needs review: gemma-4-e2b-it-nvidia-vllm-single”GitHub · Nov 3, 2026
- laxshmate/genmodelfit“すべての環境で検出できるようにする(41 通りの環境の洗い出し・GB10・WSL2 の AMD/Intel・GPU 名は表でなく文法で)”GitHub · Oct 27, 2026
- CarstVaartjes/vonk-forge-recipes“Refresh qwen3-8b-nvfp4-nvidia-sglang-single to the newest upstream pins”GitHub · Oct 13, 2026
- CarstVaartjes/vonk-forge-recipes“Refresh qwen3-8b-fp8-nvidia-vllm-single to the newest upstream pins”GitHub · Oct 13, 2026
The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 50
Talked about on GitHub (50 times).
On GitHub · 50
- Nov 3, 2026Refresh needs review: gemma-4-e4b-it-nvidia-vllm-single — CarstVaartjes/vonk-forge-recipes0 reactions · 1 comment
- Nov 3, 2026Refresh needs review: gemma-4-e2b-it-nvidia-vllm-single — CarstVaartjes/vonk-forge-recipes0 reactions · 1 comment
- Oct 27, 2026すべての環境で検出できるようにする(41 通りの環境の洗い出し・GB10・WSL2 の AMD/Intel・GPU 名は表でなく文法で) — laxshmate/genmodelfit0 reactions
- Oct 13, 2026Refresh qwen3-8b-nvfp4-nvidia-sglang-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions · 1 comment
- Oct 13, 2026Refresh qwen3-8b-fp8-nvidia-vllm-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions · 1 comment
45 more on GitHub
- Oct 13, 2026Refresh qwen3-8b-fp8-nvidia-trtllm-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh qwen3-8b-fp8-nvidia-sglang-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh qwen3-6-35b-a3b-mtp-q4-k-xl-nvidia-llamacpp-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh qwen3-6-35b-a3b-mtp-q4-k-xl-nvidia-llamacpp-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh qwen3-32b-nvfp4-nvidia-vllm-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh qwen3-32b-nvfp4-nvidia-trtllm-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh qwen3-32b-nvfp4-nvidia-sglang-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh qwen3-30b-a3b-nvfp4-nvidia-trtllm-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh qwen3-14b-nvfp4-nvidia-vllm-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh qwen3-14b-nvfp4-nvidia-trtllm-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh qwen3-14b-nvfp4-nvidia-sglang-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh qwen3-14b-fp8-nvidia-vllm-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh qwen3-14b-fp8-nvidia-trtllm-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh qwen3-14b-fp8-nvidia-sglang-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh qwen2-5-vl-7b-instruct-nvfp4-nvidia-vllm-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh phi-4-reasoning-plus-nvfp4-nvidia-vllm-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh phi-4-reasoning-plus-nvfp4-nvidia-sglang-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh phi-4-reasoning-plus-fp8-nvidia-vllm-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh phi-4-reasoning-plus-fp8-nvidia-sglang-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh phi-4-multimodal-instruct-nvfp4-nvidia-vllm-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh phi-4-multimodal-instruct-nvfp4-nvidia-sglang-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh phi-4-multimodal-instruct-fp8-nvidia-vllm-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions · 1 comment
- Oct 13, 2026Refresh phi-4-multimodal-instruct-fp8-nvidia-sglang-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh nemotron-3-nano-omni-30b-a3b-bf16-nvidia-sglang-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh nemotron-3-nano-30b-a3b-fp8-nvidia-vllm-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh nemotron-3-nano-30b-a3b-bf16-nvidia-vllm-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh llama-3-3-70b-instruct-nvfp4-nvidia-vllm-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh llama-3-3-70b-instruct-nvfp4-nvidia-sglang-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh llama-3-3-70b-instruct-nvfp4-nvidia-sglang-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh llama-3-1-8b-instruct-nvfp4-nvidia-vllm-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh llama-3-1-8b-instruct-nvfp4-nvidia-sglang-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh llama-3-1-8b-instruct-fp8-nvidia-vllm-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh llama-3-1-8b-instruct-fp8-nvidia-vllm-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh llama-3-1-8b-instruct-fp8-nvidia-sglang-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh llama-3-1-405b-instruct-awq-int4-nvidia-vllm-dual to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 13, 2026Refresh gpt-oss-20b-nvidia-vllm-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 12, 2026Refresh gpt-oss-20b-nvidia-trtllm-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 12, 2026Refresh gpt-oss-20b-nvidia-sglang-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 12, 2026Refresh gpt-oss-120b-nvidia-vllm-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 12, 2026Refresh gpt-oss-120b-nvidia-trtllm-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 12, 2026Refresh gpt-oss-120b-nvidia-sglang-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 12, 2026Refresh gpt-oss-120b-nvidia-trtllm-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 12, 2026Refresh gpt-oss-120b-nvidia-sglang-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 12, 2026Refresh gpt-oss-120b-eagle3-nvidia-trtllm-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
- Oct 12, 2026Refresh gemma-4-e4b-it-nvidia-vllm-single to the newest upstream pins — CarstVaartjes/vonk-forge-recipes0 reactions
In this repository29 other files it gives its agents.
- nvidia/playbook-dgx-station-ai-skills/assets/AGENTS.mdAGENTS.md
- nvidia/station-ai-skills/assets/AGENTS.mdAGENTS.md
- nvidia/station-txt2kg/assets/.cursor/rules/nextjs.mdcCursor rule
- nvidia/txt2kg/assets/.cursor/rules/nextjs.mdcCursor rule
- dgx-station-diagnoseSkill
- dgx-station-inferenceSkill
- dgx-station-migSkill
- dgx-stationSkill
- analysis-methodsSkill
- case-summarySkill
- clinical-delegationSkill
- clinical-knowledgeSkill
- cohort-compareSkill
- fhir-basicsSkill
- molecular-vizSkill
- dgx-diagnoseSkill
- dgx-station-diagnoseSkill
- dgx-station-inferenceSkill
- dgx-stationSkill
- mig-configureSkill
- sglang-setupSkill
- vllm-setupSkill
- analysis-methodsSkill
- case-summarySkill
- clinical-delegationSkill
- clinical-knowledgeSkill
- cohort-compareSkill
- fhir-basicsSkill
- molecular-vizSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 9 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Treat inspection and planning as read-only.
- Distinctive: line 13
Search the playbooks for the user's MIG concern and cite relevant results.
- Very specific: line 14
Read compatibility.capabilities.mig_inspection.
- Very specific: line 15
Run mig inspect and mig profiles.
- Very specific: line 16
Before planning, require compatibility.capabilities.mig_mutation to be true.
- Distinctive: line 20
If any client is active, stop.
- Distinctive: line 27
Never use a hardcoded GPU index, profile table, or assumed placement.
- Distinctive: line 28
Never destroy instances, reset a GPU, reboot, or change MIG mode outside an approved plan.
- Distinctive: line 29
Never kill a GPU process or take over a service.
- Distinctive: line 31
Do not improvise further mutations after partial failure.
- Distinctive: line 32
Do not treat Fabric Manager as a normal Station prerequisite.
- Very specific: line 33
Treat --yes only as approval already obtained.
- Distinctive: line 35
Read references/workflow.md before planning or applying a layout.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
DGX Station MIG
Treat inspection and planning as read-only. Treat every apply as disruptive.
Workflow
- Run
scripts/dgx-assist system inspect --json. - Search the playbooks for the user's MIG concern and cite relevant results.
- Read
compatibility.capabilities.mig_inspection. If it is false, stop and explain that the detected release has no MIG inspection profile. - Run
mig inspectandmig profiles. Use only profiles reported by the installed driver. This read-only step is available on the recognized Software 1.0 and Software 2.0 profiles. - Before planning, require
compatibility.capabilities.mig_mutationto betrue. If it is false, report the observed state but do not suggest a layout or work around the restriction. - Require the desired exact layout. Do not choose a layout from model names or nominal memory sums.
- Run
mig plan --layout "<layout>". - Present current and proposed state, exact commands, active clients, privilege, workload impact, reset/reboot possibility, and restoration commands.
- If any client is active, stop. Tell the user dgx-assist will not terminate it.
- Obtain explicit confirmation immediately before mutation.
- Run
mig apply --plan-id "<id>" --yes. - Report every verified MIG UUID. On partial failure, stop and present only the recorded restoration plan.
Safety requirements
- Never use a hardcoded GPU index, profile table, or assumed placement.
- Never destroy instances, reset a GPU, reboot, or change MIG mode outside an approved plan.
- Never kill a GPU process or take over a service.
- Invalidate the plan when clients, mode, profiles, release, driver, or instances change.
- Do not improvise further mutations after partial failure.
- Do not treat Fabric Manager as a normal Station prerequisite.
- Treat
--yesonly as approval already obtained.
Read references/workflow.md before planning or applying a layout.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

