Skip to content

chore: publish NeMo MBridge skills#151

Merged
mosheabr merged 1 commit into
NVIDIA:mainfrom
cuichenx:chore/nemo-mbridge-component-entry
May 29, 2026
Merged

chore: publish NeMo MBridge skills#151
mosheabr merged 1 commit into
NVIDIA:mainfrom
cuichenx:chore/nemo-mbridge-component-entry

Conversation

@cuichenx
Copy link
Copy Markdown
Contributor

@cuichenx cuichenx commented May 29, 2026

Onboarding type

  • New product onboarding (new components.d/<slug>.yml file)
  • Other (catalog change, README fix, infrastructure, etc.)

This replaces the existing megatron-bridge component slug with nemo-mbridge and registers the signed NeMo MBridge skills for automated catalog sync. It follows the flat, explicit skill-entry pattern used by components.d/nemo-automodel.yml without manually adding catalog skill content in this PR.

For new product onboarding — author affirmations

By submitting this PR, I confirm on behalf of my team:

  • Skills cleared for open source release per NVIDIA's internal IP review process (six-question check, all answers affirmative)
  • License selected: Apache 2.0 / CC-BY 4.0 / Dual (Apache 2.0 + CC-BY 4.0). Specify: Apache-2.0, matching the 20 upstream SKILL.md frontmatter entries
  • No new license or new third-party component introduced beyond what the source repo already carries
  • Source repo is public and under an NVIDIA-owned GitHub org
  • .agents/skills/ or skills/ path used for new entries (or existing path retained for legacy entries per components.d/<slug>.yml)

Maintainer follow-up before review: please confirm the two unchecked internal/IP-review affirmations above.

Reviewer checklist (OSS Skills PIC)

  • Author confirmations above are checked
  • components.d/<slug>.yml entry valid (required fields, unique catalog_dir, path exists in source repo, filename slug matches name)
  • SKILL.md frontmatter spec-compliant (at least one sampled)
  • No new license or third-party dependency requiring OSRB filing

All PRs

  • All commits signed off with DCO (git commit -s).
    If you forgot, run git rebase --signoff origin/main && git push --force-with-lease to retroactively sign all commits in your branch.

Other context (for non-onboarding PRs)

Changes:

  • Rename component slug file from components.d/megatron-bridge.yml to components.d/nemo-mbridge.yml.
  • Change display name to NeMo MBridge.
  • Follow the NeMo AutoModel pattern: one explicit customer-facing skill path per skills: entry and flat catalog_dir values.
  • Register all 20 signed skills/nemo-mbridge-* directories from NVIDIA-NeMo/Megatron-Bridge for the automated sync workflow.

This PR intentionally does not add files under skills/ or update README.md; those are generated by the sync workflow after the component entry merges.

Validation run locally:

  • Parsed components.d/nemo-mbridge.yml and verified 20 entries.
  • Verified every entry uses path: skills/<catalog_dir>/.

Signed-off-by: Chen Cui <chcui@nvidia.com>
@cuichenx cuichenx force-pushed the chore/nemo-mbridge-component-entry branch from c1e6ca9 to 74c743d Compare May 29, 2026 17:30
Copy link
Copy Markdown
Collaborator

@mosheabr mosheabr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved. All 20 NeMo MBridge skills (nemo-mbridge-*) verified 5/5 in NVIDIA-NeMo/Megatron-Bridge — sig + skill-card + evals + BENCHMARK across the board. Largest single-shot signing push of the catalog so far. Flat layout, lowercase, product-prefixed names, license-specify clean. Will follow up with orphan cleanup of skills/Megatron-Bridge/ in a separate PR (same pattern as DeepStream).

@mosheabr mosheabr merged commit d8829d8 into NVIDIA:main May 29, 2026
2 checks passed
mosheabr added a commit that referenced this pull request May 29, 2026
PR #151 migrated NeMo MBridge to flat layout: the new
components.d/nemo-mbridge.yml registers 20 skills at flat top-level
paths (skills/nemo-mbridge-*/) and the old components.d/megatron-bridge.yml
sweep entry was deleted.

The previous catalog content under skills/Megatron-Bridge/ (a single
nested skill mbridge-recipe-recommender from the legacy layout) was
left behind by the sync — anti-pattern #1: sync writes content for
referenced paths but does not garbage-collect directories that are no
longer referenced by any components.d entry.

Removing it here completes the migration. Authoritative content for
NeMo MBridge now lives at skills/nemo-mbridge-*/ once the next sync
runs, with no duplicate or stale path.

Signed-off-by: Moshe Abramovitch <moshea@nvidia.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants