nemo-mbridge-multi-node-slurm skillB
nemo-mbridge-multi-node-slurm is agent-read markdown (skill) from nvidia/skills: Convert single-node scripts to multi-node Slurm sbatch jobs and debug common multi-node failures. Covers srun-native vs uv run torch.distributed approaches, container setup, NCCL timeouts, OOM sizing for MoE models, and interactive allocation..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Multi-Node Slurm Convert single-node `uv run python -m torch.distributed.run` commands into multi-node Slurm sbatch scripts with Enroot container support, and debug common multi-node failures. ## First Answer Checklist When converting or debugging Bridge multi-node jobs, answer in this order: 1. Prefer the **srun-native** launch shape for Bridge scripts that reach `initialize.py`: `#SBATCH --ntasks-per-node=8` and a direct `srun ... uv run python <script> ...` launch. Do not wrap these jobs in `python -m torch.distributed.run`. 2. State that Bridge derives `RANK`, `WORLD_SIZE`, `LOCAL_RANK`, `MASTER_ADDR`, and `MASTER_PORT` from SLURM variables during `initialize.py` distributed init. 3. Require shared paths and matching container mounts for the repo, data, logs, `HF_HOME`, `UV_CACHE_DIR`, and `NEMO_HOME`. 4. For NCCL timeout reports, do these first-log checks before speculating: - grep for real errors while filtering warning/frame noise - inspect `Failures:` to find the first failed rank and node - grep for `ncclUniqueId`, `timeout`, or `crash on rank 0` ## Two Approaches: srun-native vs uv run torch.distributed …
Read the whole file at its exact version.
How to install
mdr add nvidia/skills/nemo-mbridge-multi-node-slurm@git:20260602.e695a83mdr add nvidia/skills/nemo-mbridge-multi-node-slurm@sha256:1755991a2310d06dPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_ci2cxuvvadrr77mg)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260602.e695a83 latest | 2026-06-02 | e695a83 | 15,784 B | B | view · diff |
| git:20260529.7d99fda | 2026-05-29 | 7d99fda | 16,414 B | B | view |
Audit of the latest version
- fail: No script tag (matched: <script)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (15784 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
Source
nvidia/skills · 3,415 stars · license Apache-2.0 · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ci2cxuvvadrr77mg GET https://markdownregistry.com/api/v1/resolve?ref=nvidia/skills/nemo-mbridge-multi-node-slurm GET https://markdownregistry.com/api/v1/blob/1755991a2310d06d8a98d8576b14ce7e8b14c6bddb0901c4a1eb11350be64535
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.