
Description
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.
SKILL.md
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.
More skills from the dgx-spark-playbooks repository
View all 15 skillsanalysis-methods
write Python analysis code for FHIR data
Jul 14Data AnalysisFHIRHealthcareNVIDIA +1case-summary
summarize clinical patient cases from FHIR
Jul 14FHIRHealthcareNVIDIASummarizationclinical-delegation
delegate clinical tasks to specialist agents
Jul 14AgentsHealthcareMulti-AgentNVIDIAclinical-knowledge
provide clinical reference and regulatory context
Jul 14Clinical TrialsHealthcareNVIDIARegulatory Compliancecohort-compare
analyze patient cohorts from FHIR endpoints
Jul 14Data AnalysisFHIRHealthcareNVIDIAdgx-diagnose
diagnose NVIDIA DGX Station hardware issues
Jul 14AI InfrastructureDebuggingNVIDIAObservability
More from NVIDIA
View publishernemoclaw-user-guide
retrieve NemoClaw documentation and configuration
NemoClaw
Jul 20DocumentationMCPSearchmcore-build-and-dependency
manage Megatron-LM development environments
Megatron-LM
Jul 27ContainersDeploymentPythonmcore-bump-base-image
update NVIDIA PyTorch base images
Megatron-LM
Jul 14CI/CDDeploymentmcore-cicd
manage CI/CD pipelines for Megatron-LM
Megatron-LM
Jul 27CI/CDDeploymentGitHubmcore-create-issue
investigate CI failures and create issues
Megatron-LM
Jul 14DebuggingGitHubTriagemcore-linting-and-formatting
lint and format Megatron-LM code
Megatron-LM
Jul 14Best PracticesCode Analysis