[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-nvidia-dgx-station-diagnose":3,"mdc-91qk1l-key":34,"related-repo-nvidia-dgx-station-diagnose":252,"related-org-nvidia-dgx-station-diagnose":354},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":23,"repoUrl":24,"updatedAt":25,"license":26,"forks":27,"topics":28,"repo":29,"sourceUrl":32,"mdContent":33},"dgx-station-diagnose","diagnose NVIDIA DGX Station health","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.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},"nvidia","NVIDIA","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fnvidia.png",[12,16,19,20],{"name":13,"slug":14,"type":15},"Observability","observability","tag",{"name":17,"slug":18,"type":15},"Operations","operations",{"name":9,"slug":8,"type":15},{"name":21,"slug":22,"type":15},"Debugging","debugging",1144,"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fdgx-spark-playbooks","2026-08-05T05:58:15.993245",null,249,[],{"repoUrl":24,"stars":23,"forks":27,"topics":30,"description":31},[],"Collection of step-by-step playbooks for setting up AI\u002FML workloads on NVIDIA DGX Spark devices with Blackwell architecture.","https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fdgx-spark-playbooks\u002Ftree\u002FHEAD\u002Fnvidia\u002Fstation-ai-skills\u002Fassets\u002Fskills\u002Fdgx-station-diagnose","---\nname: dgx-station-diagnose\ndescription: 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.\n---\n\n# DGX Station diagnostics\n\nDiagnose first. Do not mutate as part of diagnosis.\n\n## Workflow\n\n1. Run `scripts\u002Fdgx-assist diagnose run --json`.\n2. Report the detected compatibility profile, then findings in severity order with their stable IDs and evidence. Preserve `unknown` states. On Software 1.0, do not reinterpret intentionally skipped Software 2.0 service checks as faults.\n3. Search the pinned playbooks for each high or critical finding; cite the relevant URL, heading, lines, and commit.\n4. If no passage overlaps, say so and avoid inventing a platform fix.\n5. Offer `diagnose bundle --report-id \"\u003Cid>\"` when escalation is appropriate.\n6. Offer at most one automatic fix at a time, and only when `fix_id` is present.\n7. Preview with `diagnose fix --report-id \"\u003Cid>\" --finding \"\u003Cid>\" --dry-run`.\n8. Explain exact actions, impact, privilege, and reboot state. Obtain explicit approval.\n9. Repeat with `--yes` only after approval and report the action receipt.\n\n## Safety requirements\n\n- Keep `diagnose run` read-only.\n- Never install packages, rewrite Docker configuration, change power caps or driver parameters, kill workloads, or modify MIG through a diagnostic fix.\n- Never stop a service without current `dgx-assist` ownership evidence.\n- Never use Fabric Manager as a routine Station check or remediation.\n- Re-run diagnostics when finding evidence is stale.\n- Never reveal secrets or unredacted home paths in a bundle.\n- Do not execute an unregistered remediation.\n- Treat `--yes` only as approval already obtained.\n\nRead [references\u002Ffindings.md](references\u002Ffindings.md) before proposing a fix or support bundle. Read [references\u002Fbringup.md](references\u002Fbringup.md) when the problem concerns physical deployment, BMC or firmware verification, driver bring-up, power braking, or support escalation.\n",{"data":35,"body":36},{"name":4,"description":6},{"type":37,"children":38},"root",[39,48,54,61,159,165,232],{"type":40,"tag":41,"props":42,"children":44},"element","h1",{"id":43},"dgx-station-diagnostics",[45],{"type":46,"value":47},"text","DGX Station diagnostics",{"type":40,"tag":49,"props":50,"children":51},"p",{},[52],{"type":46,"value":53},"Diagnose first. Do not mutate as part of diagnosis.",{"type":40,"tag":55,"props":56,"children":58},"h2",{"id":57},"workflow",[59],{"type":46,"value":60},"Workflow",{"type":40,"tag":62,"props":63,"children":64},"ol",{},[65,80,93,98,103,116,129,141,146],{"type":40,"tag":66,"props":67,"children":68},"li",{},[69,71,78],{"type":46,"value":70},"Run ",{"type":40,"tag":72,"props":73,"children":75},"code",{"className":74},[],[76],{"type":46,"value":77},"scripts\u002Fdgx-assist diagnose run --json",{"type":46,"value":79},".",{"type":40,"tag":66,"props":81,"children":82},{},[83,85,91],{"type":46,"value":84},"Report the detected compatibility profile, then findings in severity order with their stable IDs and evidence. Preserve ",{"type":40,"tag":72,"props":86,"children":88},{"className":87},[],[89],{"type":46,"value":90},"unknown",{"type":46,"value":92}," states. On Software 1.0, do not reinterpret intentionally skipped Software 2.0 service checks as faults.",{"type":40,"tag":66,"props":94,"children":95},{},[96],{"type":46,"value":97},"Search the pinned playbooks for each high or critical finding; cite the relevant URL, heading, lines, and commit.",{"type":40,"tag":66,"props":99,"children":100},{},[101],{"type":46,"value":102},"If no passage overlaps, say so and avoid inventing a platform fix.",{"type":40,"tag":66,"props":104,"children":105},{},[106,108,114],{"type":46,"value":107},"Offer ",{"type":40,"tag":72,"props":109,"children":111},{"className":110},[],[112],{"type":46,"value":113},"diagnose bundle --report-id \"\u003Cid>\"",{"type":46,"value":115}," when escalation is appropriate.",{"type":40,"tag":66,"props":117,"children":118},{},[119,121,127],{"type":46,"value":120},"Offer at most one automatic fix at a time, and only when ",{"type":40,"tag":72,"props":122,"children":124},{"className":123},[],[125],{"type":46,"value":126},"fix_id",{"type":46,"value":128}," is present.",{"type":40,"tag":66,"props":130,"children":131},{},[132,134,140],{"type":46,"value":133},"Preview with ",{"type":40,"tag":72,"props":135,"children":137},{"className":136},[],[138],{"type":46,"value":139},"diagnose fix --report-id \"\u003Cid>\" --finding \"\u003Cid>\" --dry-run",{"type":46,"value":79},{"type":40,"tag":66,"props":142,"children":143},{},[144],{"type":46,"value":145},"Explain exact actions, impact, privilege, and reboot state. Obtain explicit approval.",{"type":40,"tag":66,"props":147,"children":148},{},[149,151,157],{"type":46,"value":150},"Repeat with ",{"type":40,"tag":72,"props":152,"children":154},{"className":153},[],[155],{"type":46,"value":156},"--yes",{"type":46,"value":158}," only after approval and report the action receipt.",{"type":40,"tag":55,"props":160,"children":162},{"id":161},"safety-requirements",[163],{"type":46,"value":164},"Safety requirements",{"type":40,"tag":166,"props":167,"children":168},"ul",{},[169,182,187,200,205,210,215,220],{"type":40,"tag":66,"props":170,"children":171},{},[172,174,180],{"type":46,"value":173},"Keep ",{"type":40,"tag":72,"props":175,"children":177},{"className":176},[],[178],{"type":46,"value":179},"diagnose run",{"type":46,"value":181}," read-only.",{"type":40,"tag":66,"props":183,"children":184},{},[185],{"type":46,"value":186},"Never install packages, rewrite Docker configuration, change power caps or driver parameters, kill workloads, or modify MIG through a diagnostic fix.",{"type":40,"tag":66,"props":188,"children":189},{},[190,192,198],{"type":46,"value":191},"Never stop a service without current ",{"type":40,"tag":72,"props":193,"children":195},{"className":194},[],[196],{"type":46,"value":197},"dgx-assist",{"type":46,"value":199}," ownership evidence.",{"type":40,"tag":66,"props":201,"children":202},{},[203],{"type":46,"value":204},"Never use Fabric Manager as a routine Station check or remediation.",{"type":40,"tag":66,"props":206,"children":207},{},[208],{"type":46,"value":209},"Re-run diagnostics when finding evidence is stale.",{"type":40,"tag":66,"props":211,"children":212},{},[213],{"type":46,"value":214},"Never reveal secrets or unredacted home paths in a bundle.",{"type":40,"tag":66,"props":216,"children":217},{},[218],{"type":46,"value":219},"Do not execute an unregistered remediation.",{"type":40,"tag":66,"props":221,"children":222},{},[223,225,230],{"type":46,"value":224},"Treat ",{"type":40,"tag":72,"props":226,"children":228},{"className":227},[],[229],{"type":46,"value":156},{"type":46,"value":231}," only as approval already obtained.",{"type":40,"tag":49,"props":233,"children":234},{},[235,237,243,245,250],{"type":46,"value":236},"Read ",{"type":40,"tag":238,"props":239,"children":241},"a",{"href":240},"references\u002Ffindings.md",[242],{"type":46,"value":240},{"type":46,"value":244}," before proposing a fix or support bundle. Read ",{"type":40,"tag":238,"props":246,"children":248},{"href":247},"references\u002Fbringup.md",[249],{"type":46,"value":247},{"type":46,"value":251}," when the problem concerns physical deployment, BMC or firmware verification, driver bring-up, power braking, or support escalation.",{"items":253,"total":353},[254,274,287,302,317,328,341],{"slug":255,"name":255,"fn":256,"description":257,"org":258,"tags":259,"stars":23,"repoUrl":24,"updatedAt":273},"analysis-methods","write Python analysis code for FHIR data","Teaches the analyst agent how to write correct, robust Python analysis code for FHIR clinical data using pandas, matplotlib, and scipy.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[260,263,266,269,270],{"name":261,"slug":262,"type":15},"Data Analysis","data-analysis",{"name":264,"slug":265,"type":15},"FHIR","fhir",{"name":267,"slug":268,"type":15},"Healthcare","healthcare",{"name":9,"slug":8,"type":15},{"name":271,"slug":272,"type":15},"Python","python","2026-07-14T05:35:59.037962",{"slug":275,"name":275,"fn":276,"description":277,"org":278,"tags":279,"stars":23,"repoUrl":24,"updatedAt":286},"case-summary","summarize clinical patient cases from FHIR","Prepare a complete clinical case summary for a patient from FHIR endpoints. Use when asked to summarize a patient, compile a case, or prepare for tumor board.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[280,281,282,283],{"name":264,"slug":265,"type":15},{"name":267,"slug":268,"type":15},{"name":9,"slug":8,"type":15},{"name":284,"slug":285,"type":15},"Summarization","summarization","2026-07-14T05:35:52.790528",{"slug":288,"name":288,"fn":289,"description":290,"org":291,"tags":292,"stars":23,"repoUrl":24,"updatedAt":301},"clinical-delegation","delegate clinical tasks to specialist agents","How to delegate clinical tasks to specialist agents. Always use sub-agent runtime with explicit agentId — never ACP. Never call FHIR via web_fetch.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[293,296,297,300],{"name":294,"slug":295,"type":15},"Agents","agents",{"name":267,"slug":268,"type":15},{"name":298,"slug":299,"type":15},"Multi-Agent","multi-agent",{"name":9,"slug":8,"type":15},"2026-07-14T05:35:55.294972",{"slug":303,"name":303,"fn":304,"description":305,"org":306,"tags":307,"stars":23,"repoUrl":24,"updatedAt":316},"clinical-knowledge","provide clinical reference and regulatory context","Teaches agents clinical reference ranges, condition codes, quality measure definitions, drug classifications, and regulatory context so they can flag abnormal values and identify care gaps.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[308,311,312,313],{"name":309,"slug":310,"type":15},"Clinical Trials","clinical-trials",{"name":267,"slug":268,"type":15},{"name":9,"slug":8,"type":15},{"name":314,"slug":315,"type":15},"Regulatory Compliance","regulatory-compliance","2026-07-14T05:35:56.550833",{"slug":318,"name":318,"fn":319,"description":320,"org":321,"tags":322,"stars":23,"repoUrl":24,"updatedAt":327},"cohort-compare","analyze patient cohorts from FHIR endpoints","Analyze a cohort of patients from FHIR endpoints to find care gaps and patterns. Use when asked to compare patients, find quality gaps, or analyze a population.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[323,324,325,326],{"name":261,"slug":262,"type":15},{"name":264,"slug":265,"type":15},{"name":267,"slug":268,"type":15},{"name":9,"slug":8,"type":15},"2026-07-14T05:35:51.543095",{"slug":329,"name":329,"fn":330,"description":331,"org":332,"tags":333,"stars":23,"repoUrl":24,"updatedAt":340},"dgx-diagnose","diagnose NVIDIA DGX Station hardware issues","Diagnose common DGX Station GB300 issues — CUDA crashes, wrong-GPU targeting, vLLM\u002FSGLang container bugs, MIG state problems, NVLink\u002FFabric Manager errors, X\u002FVulkan failures, HuggingFace auth, and port conflicts. Use when the user reports a GPU error, inference server crash, MIG problem, or any unexplained DGX Station failure.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[334,337,338,339],{"name":335,"slug":336,"type":15},"AI Infrastructure","ai-infrastructure",{"name":21,"slug":22,"type":15},{"name":9,"slug":8,"type":15},{"name":13,"slug":14,"type":15},"2026-07-14T05:31:04.085598",{"slug":342,"name":342,"fn":343,"description":344,"org":345,"tags":346,"stars":23,"repoUrl":24,"updatedAt":352},"dgx-station","manage NVIDIA DGX Station development","Inspect and guide NVIDIA DGX Station GB300 development using the local dgx-assist CLI and pinned NVIDIA playbooks. Use for general Station platform questions, Software 1.0 or 2.0 compatibility, GB300 or RTX GPU selection, UUID ordering, mixed ATS\u002FHMM coherency, CDMM, general containers, CDI, CUDA visibility, or vsloshd power-sloshing behavior. Do not use for vLLM or SGLang container selection or tuning, serving a named model, changing MIG, or troubleshooting a reported failure when the dedicated Station skill applies.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[347,350,351],{"name":348,"slug":349,"type":15},"CLI","cli",{"name":9,"slug":8,"type":15},{"name":17,"slug":18,"type":15},"2026-08-05T05:58:16.736667",15,{"items":355,"total":510},[356,374,390,401,413,425,438,452,465,476,490,499],{"slug":357,"name":357,"fn":358,"description":359,"org":360,"tags":361,"stars":371,"repoUrl":372,"updatedAt":373},"nemoclaw-user-guide","retrieve NemoClaw documentation and configuration","Guides human users' AI agents to the NemoClaw docs MCP server and canonical Fern documentation in Markdown form. Use when users ask how to install, configure, operate, troubleshoot, secure, or learn NemoClaw with an AI coding assistant. Trigger keywords - nemoclaw docs, use nemoclaw with ai agent, nemoclaw mcp docs, nemoclaw install help, nemoclaw quickstart, nemoclaw markdown docs, llms.txt, agent skills.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[362,365,368],{"name":363,"slug":364,"type":15},"Documentation","documentation",{"name":366,"slug":367,"type":15},"MCP","mcp",{"name":369,"slug":370,"type":15},"Search","search",21777,"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FNemoClaw","2026-07-20T06:00:01.461044",{"slug":375,"name":375,"fn":376,"description":377,"org":378,"tags":379,"stars":387,"repoUrl":388,"updatedAt":389},"mcore-build-and-dependency","manage Megatron-LM development environments","Container-based dev environment setup and dependency management for Megatron-LM. Covers acquiring and launching the CI container, uv package management, and updating uv.lock.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[380,383,386],{"name":381,"slug":382,"type":15},"Containers","containers",{"name":384,"slug":385,"type":15},"Deployment","deployment",{"name":271,"slug":272,"type":15},17049,"https:\u002F\u002Fgithub.com\u002FNVIDIA\u002FMegatron-LM","2026-07-27T06:06:11.249662",{"slug":391,"name":391,"fn":392,"description":393,"org":394,"tags":395,"stars":387,"repoUrl":388,"updatedAt":400},"mcore-bump-base-image","update NVIDIA PyTorch base images","Bump the NVIDIA PyTorch base image (`nvcr.io\u002Fnvidia\u002Fpytorch:YY.MM-py3`) used by Megatron-LM CI. Covers the two pin sites (GitHub CI in `docker\u002F.ngc_version.dev` and GitLab CI in `.gitlab\u002Fstages\u002F01.build.yml`), the post-bump CI loop (re-run functional tests, refresh golden values, mark broken tests), and the gotchas that bit PRs",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[396,399],{"name":397,"slug":398,"type":15},"CI\u002FCD","ci-cd",{"name":384,"slug":385,"type":15},"2026-07-14T05:25:59.97109",{"slug":402,"name":402,"fn":403,"description":404,"org":405,"tags":406,"stars":387,"repoUrl":388,"updatedAt":412},"mcore-cicd","manage CI\u002FCD pipelines for Megatron-LM","CI\u002FCD reference for Megatron-LM. Covers CI pipeline structure, PR scope labels, triggering internal GitLab CI (which force-pushes the current branch to a pull-request\u002FBRANCH ref — always dry-run and verify the destination first; never run against shared or protected branches), and CI failure investigation.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[407,408,409],{"name":397,"slug":398,"type":15},{"name":384,"slug":385,"type":15},{"name":410,"slug":411,"type":15},"GitHub","github","2026-07-27T06:06:12.278222",{"slug":414,"name":414,"fn":415,"description":416,"org":417,"tags":418,"stars":387,"repoUrl":388,"updatedAt":424},"mcore-create-issue","investigate CI failures and create issues","Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[419,420,421],{"name":21,"slug":22,"type":15},{"name":410,"slug":411,"type":15},{"name":422,"slug":423,"type":15},"Triage","triage","2026-07-14T05:25:57.442089",{"slug":426,"name":426,"fn":427,"description":428,"org":429,"tags":430,"stars":387,"repoUrl":388,"updatedAt":437},"mcore-linting-and-formatting","lint and format Megatron-LM code","Linting and formatting for Megatron-LM. Covers running autoformat.sh, tools (ruff, black, isort, pylint, mypy), and code style rules.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[431,434],{"name":432,"slug":433,"type":15},"Best Practices","best-practices",{"name":435,"slug":436,"type":15},"Code Analysis","code-analysis","2026-07-14T05:25:56.18433",{"slug":439,"name":439,"fn":440,"description":441,"org":442,"tags":443,"stars":387,"repoUrl":388,"updatedAt":451},"mcore-migrate-gpt-to-hybrid","migrate Megatron-LM models to HybridModel","Migration guide for moving Megatron Core GPTModel checkpoints, model providers, training commands, and layer mappings to HybridModel.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[444,447,450],{"name":445,"slug":446,"type":15},"Machine Learning","machine-learning",{"name":448,"slug":449,"type":15},"Migration","migration",{"name":9,"slug":8,"type":15},"2026-07-17T06:07:11.777011",{"slug":453,"name":453,"fn":454,"description":455,"org":456,"tags":457,"stars":387,"repoUrl":388,"updatedAt":464},"mcore-onboard-gb200-1node-tests","onboard functional tests for GB200","Onboard 1-node GitHub MR functional tests for GB200 from existing mr-scoped 2-node tests.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[458,461],{"name":459,"slug":460,"type":15},"QA","qa",{"name":462,"slug":463,"type":15},"Testing","testing","2026-07-14T05:25:53.673039",{"slug":466,"name":466,"fn":467,"description":468,"org":469,"tags":470,"stars":387,"repoUrl":388,"updatedAt":475},"mcore-run-on-slurm","launch distributed training jobs on SLURM","How to launch distributed Megatron-LM training jobs on a SLURM cluster. Covers a minimal sbatch skeleton, environment-variable setup for torch.distributed.run, CUDA_DEVICE_MAX_CONNECTIONS rules across hardware and parallelism modes, container conventions, monitoring, and per-rank failure diagnosis.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[471,472],{"name":384,"slug":385,"type":15},{"name":473,"slug":474,"type":15},"Infrastructure","infrastructure","2026-07-14T05:25:49.362534",{"slug":477,"name":477,"fn":478,"description":479,"org":480,"tags":481,"stars":387,"repoUrl":388,"updatedAt":489},"mcore-split-pr","split pull requests to reduce review load","Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[482,485,486],{"name":483,"slug":484,"type":15},"Code Review","code-review",{"name":410,"slug":411,"type":15},{"name":487,"slug":488,"type":15},"Pull Requests","pull-requests","2026-07-14T05:26:01.226578",{"slug":491,"name":491,"fn":492,"description":493,"org":494,"tags":495,"stars":387,"repoUrl":388,"updatedAt":498},"mcore-testing","run and manage Megatron-LM tests","Test system for Megatron-LM. Covers test layout, recipe YAML structure, adding and running unit and functional tests, golden values, marker filters, and CI parity.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[496,497],{"name":459,"slug":460,"type":15},{"name":462,"slug":463,"type":15},"2026-07-14T05:25:54.928983",{"slug":500,"name":500,"fn":501,"description":502,"org":503,"tags":504,"stars":387,"repoUrl":388,"updatedAt":509},"nightly-sync","manage nightly main-to-dev sync workflows","Domain knowledge for the nightly main-to-dev sync workflow. Covers merge strategy, CI architecture, failure investigation, and known issues.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[505,508],{"name":506,"slug":507,"type":15},"Automation","automation",{"name":397,"slug":398,"type":15},"2026-07-30T05:29:03.275638",525]