BF nemo-mbridge-recipe-recommender
Recommend and customize Megatron Bridge library and benchmark recipes for a user's model, GPU count, hardware, sequence length, and pretrain/SFT/PEFT goal. Use when selecting a starting recipe, comparing library and benchmark configs, resizing parallelism for a GPU allocation, or distinguishing convergence changes, semantics-preserving execution tuning, and benchmark-only shortcuts.
Recommend and customize Megatron Bridge library and benchmark recipes for a user's model, GPU count, hardware, sequence length, and pretrain/SFT/PEFT goal.
As a process F 36/100 · Will not run — References files that are not bundled: references/recipe-index.md, scripts/training/run_recipe.py, scripts/performance/setup_experiment.py
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/recipe-index.md - warning
missing-refreference to a missing file: scripts/training/run_recipe.py - warning
missing-refreference to a missing file: scripts/performance/setup_experiment.py - warning
missing-refreference to a missing file: scripts/performance/utils/utils.py - warning
missing-refreference to a missing file: scripts/training/train.sh - warning
missing-refreference to a missing file: scripts/performance/utils/overrides.py - note
edit-residuethe text marks something as outdated (lines 163): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 36/100
- 0Tools and files. 6 referenced file(s) missing: references/recipe-index.md, scripts/training/run_recipe.py, scripts/performance/setup_experiment.py
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 4 mutating operations with no state check
- 55Failures and branches. 1 branches
- 70Execution cost. Instruction body is 4021 tokens
- 100Steps. 25 steps
- 100Consistency. Name and required fields are in place
- low 10 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (4 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 385: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 25 items
- +4Has examples (4 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.