dgx-station-diagnose
Skill1.5k starsChanged 2 months agoApache-2.0View on GitHub
Run and interpret the complete read-only dgx-assist diagnostic suite for NVIDIA DGX Station GB300, correlate findings with pinned NVIDIA playbooks, export a redacted support bundle, and apply one separately approved allowlisted fix. Use when the user reports a Station, CUDA, GPU health, coherency, vsloshd, Docker, CDI, MIG, cache, port, or owned inference-service failure.
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-inferenceSkill
- dgx-station-migSkill
- dgx-stationSkill
- mig-configureSkill
- sglang-setupSkill
- vllm-setupSkill
- analysis-methodsSkill
- case-summarySkill
- clinical-delegationSkill
- clinical-knowledgeSkill
- cohort-compareSkill
- fhir-basicsSkill
- molecular-vizSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 7 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Search the pinned playbooks for each high or critical finding.
- Distinctive: line 15
If no passage overlaps, say so and avoid inventing a platform fix.
- Distinctive: line 25
Never install packages, rewrite Docker configuration, change power caps or driver parameters, kill workloads, or modify MIG through a …
- Very specific: line 26
Never stop a service without current dgx-assist ownership evidence.
- Distinctive: line 27
Never use Fabric Manager as a routine Station check or remediation.
- Distinctive: line 29
Never reveal secrets or unredacted home paths in a bundle.
- Distinctive: line 30
Do not execute an unregistered remediation.
- Very specific: line 31
Treat --yes only as approval already obtained.
- Distinctive: line 33
Read references/findings.md before proposing a fix or support bundle.
≈ “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 diagnostics
Diagnose first. Do not mutate as part of diagnosis.
Workflow
- Run
scripts/dgx-assist diagnose run --json. - Report the detected compatibility profile, then findings in severity order with their stable IDs and evidence. Preserve
unknownstates. On Software 1.0, do not reinterpret intentionally skipped Software 2.0 service checks as faults. - Search the pinned playbooks for each high or critical finding; cite the relevant URL, heading, lines, and commit.
- If no passage overlaps, say so and avoid inventing a platform fix.
- Offer
diagnose bundle --report-id "<id>"when escalation is appropriate. - Offer at most one automatic fix at a time, and only when
fix_idis present. - Preview with
diagnose fix --report-id "<id>" --finding "<id>" --dry-run. - Explain exact actions, impact, privilege, and reboot state. Obtain explicit approval.
- Repeat with
--yesonly after approval and report the action receipt.
Safety requirements
- Keep
diagnose runread-only. - Never install packages, rewrite Docker configuration, change power caps or driver parameters, kill workloads, or modify MIG through a diagnostic fix.
- Never stop a service without current
dgx-assistownership evidence. - Never use Fabric Manager as a routine Station check or remediation.
- Re-run diagnostics when finding evidence is stale.
- Never reveal secrets or unredacted home paths in a bundle.
- Do not execute an unregistered remediation.
- Treat
--yesonly as approval already obtained.
Read references/findings.md before proposing a fix or support bundle. Read references/bringup.md when the problem concerns physical deployment, BMC or firmware verification, driver bring-up, power braking, or support escalation.
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.

