Ask me what skills you need
What are you building?
Tell me what you're working on and I'll find the best agent skills for you.
Reference for the Megatron Bridge CI test system — directory layout, tier semantics, script conventions, and how to add, move, or disable tests.
tests/functional_tests/launch_scripts/
h100/
active/ # H100 tests that run in CI automatically
flaky/ # H100 tests quarantined from blocking CI
gb200/
active/ # GB200 tests that run in CI automatically
flaky/ # GB200 tests quarantined from blocking CI
Scripts are named {Tier}_{Description}.sh (e.g., L0_Launch_training.sh).
Unit tests live under tests/unit_tests/ and are independent of this layout.
| Tier | Trigger | Blocking |
|---|---|---|
| L0 | Every PR, every push to main, schedule | Yes — PR cannot merge if L0 fails |
| L1 | Push to main, schedule, or PRs with needs-more-tests label | Yes |
| L2 | Schedule and workflow_dispatch only | Yes (when triggered) |
| flaky | workflow_dispatch with test_suite=all only | No — failures are informational |
H100 and GB200 each have their own L0/L1/L2/flaky jobs. Moving a test to flaky removes it from blocking CI on both hardware targets independently.
Every launch script must start with:
# CI_TIMEOUT=<minutes>
npx skills add NVIDIA/skills --skill test-systemHow clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
Clear and well structured, with only minor parts that might need a second read.
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
Mostly actionable with clear steps; only a few small gaps remain.