mcpbeat

Mcore Migrate Gpt To Hybrid

nvidia/mcore-migrate-gpt-to-hybrid

Migration guide for moving Megatron Core GPTModel checkpoints, model providers, training commands, and layer mappings to HybridModel.

475 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
17319
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/NVIDIA/Megatron-LM --skill mcore-migrate-gpt-to-hybrid

The instruction itself

4 sections, as written by the author

GPTModel to HybridModel Migration

Answer-First Migration Guidance

  • The canonical source is

docs/user-guide/hybrid-model-migration.md.

  • Read the canonical document completely before answering, planning, reviewing,

editing, converting, or training.

  • Keep migration behavior, commands, mappings, prerequisites, limitations, and

validation in the canonical document only. Do not duplicate them in this

skill.

Workflow

  • Pull the task artifact first: checkpoint metadata, model provider or config,

training command, conversion log, diff, or failure output.

  • Read the canonical migration document completely.
  • Follow only the relevant document sections. Do not invent an unsupported

migration path or silently change the target architecture.

  • Validate the result proportionately, invoking the relevant repository build

and testing skills when applicable.

  • Report the outcome and link the canonical document for human readers.

Documentation Drift

If the implementation and migration guide disagree:

  • Report the discrepancy before continuing.
  • If the task authorizes a correction, update the canonical document first.
  • Do not add a competing migration rule to this skill.

How to use it

Copy the folder

Take nvidia/mcore-migrate-gpt-to-hybrid from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.