nemo-mbridge-perf-moe-dispatcher-selection
Choose the right MoE token dispatcher (`alltoall`, DeepEP, or HybridEP) for the hardware, EP degree, and optimization stage. Summarizes patterns from DSV3, Qwen3, Qwen3-Next, and VLM bring-up work.
npx skills add NVIDIA/skills --skill nemo-mbridge-perf-moe-dispatcher-selection --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# MoE Dispatcher Selection Guide Stable docs: @docs/training/moe-optimization.md Card: @skills/nemo-mbridge-perf-moe-dispatcher-selection/card.yaml ## Quick Decision ### By hardware | Hardware | First choice | Why | |---|---|---| | H100 | DeepEP, if the runtime package is installed | Strong default for cross-node EP on Hopper | | B200 | DeepEP, if the runtime package is installed | Good first choi
What does the nemo-mbridge-perf-moe-dispatcher-selection skill do?
Choose the right MoE token dispatcher (`alltoall`, DeepEP, or HybridEP) for the hardware, EP degree, and optimization stage. Summarizes patterns from DSV3, Qwen3, Qwen3-Next, and VLM bring-up work.
How do I install it?
Run `npx skills add NVIDIA/skills --skill nemo-mbridge-perf-moe-dispatcher-selection --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From NVIDIA/skills, a repository with 2,789 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.