Agent skill

nemo-mbridge-perf-cuda-graphs

Validate and use CUDA graph capture in Megatron Bridge, including local full-iteration graphs and Transformer Engine scoped graphs for attention, MLP, and MoE modules.

NVIDIAgithub.com/NVIDIAGitHub ↗
claude-codecodexApache-2.0
Install
npx skills add NVIDIA/skills --skill nemo-mbridge-perf-cuda-graphs --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 6
SKILL.md size: 14 KB
Bundled scripts: none
Path: skills/nemo-mbridge-perf-cuda-graphs/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,789
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# CUDA Graphs Stable documentation: @docs/training/cuda-graphs.md Card: @skills/nemo-mbridge-perf-cuda-graphs/card.yaml <!-- NVSkills CI refresh: 2026-06-15. No instruction changes. --> ## What It Is CUDA graphs capture GPU operations once and replay them with minimal host-driver overhead. Bridge supports two implementations: | `cuda_graph_impl` | Mechanism | Scope support | |---|---|---| | `"loca

More from skills
All skills →
About this skill
What does the nemo-mbridge-perf-cuda-graphs skill do?

Validate and use CUDA graph capture in Megatron Bridge, including local full-iteration graphs and Transformer Engine scoped graphs for attention, MLP, and MoE modules.

How do I install it?

Run `npx skills add NVIDIA/skills --skill nemo-mbridge-perf-cuda-graphs --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.

Keep going