How do I install the Dgx Station Mig skill?

Run npx skillmds@latest add nvidia/dgx-station-mig in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Dgx Station Mig safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Dgx Station Mig?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Dgx Station Mig free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Dgx Station Mig?

NVIDIA (@nvidia) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Dgx Station Mig by nvidia — Agent Skill

Name: Dgx Station Mig
Author: NVIDIA

Dgx Station Mig

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.

NVIDIA 26a978f 4 files · 3.8 KB Updated Sep 17, 2026 2.2k repo stars

File contents

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 inspect and mig 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_mutation to be true. 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 --yes only as approval already obtained.

Read references/workflow.md before planning or applying a layout.

---name: dgx-station-migdescription: 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.---# DGX Station MIGTreat inspection and planning as read-only. Treat every apply as disruptive.## Workflow1. Run `scripts/dgx-assist system inspect --json`.2. Search the playbooks for the user's MIG concern and cite relevant results.3. Read `compatibility.capabilities.mig_inspection`. If it is false, stop and explain that the detected release has no MIG inspection profile.4. Run `mig inspect` and `mig 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.5. Before planning, require `compatibility.capabilities.mig_mutation` to be `true`. If it is false, report the observed state but do not suggest a layout or work around the restriction.6. Require the desired exact layout. Do not choose a layout from model names or nominal memory sums.7. Run `mig plan --layout "<layout>"`.8. Present current and proposed state, exact commands, active clients, privilege, workload impact, reset/reboot possibility, and restoration commands.9. If any client is active, stop. Tell the user dgx-assist will not terminate it.10. Obtain explicit confirmation immediately before mutation.11. Run `mig apply --plan-id "<id>" --yes`.12. 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 `--yes` only as approval already obtained.Read [references/workflow.md](references/workflow.md) before planning or applying a layout.

Frequently asked questions