Skip to main content

NVIDIA-NeMo/Gym

SkillsMP has collected 7 skills from NVIDIA-NeMo/Gym. Open a skill to review its source and details.

Latest recorded source activity
SkillsMP catalog refreshed
skills collected
7
GitHub stars
1,148
GitHub forks
297

Skills in this repository

1 occupation categories · 86% classified

Showing 7 of 7 collected skills.

occupation
Software Developers
description

Use to help users get started with Nemo Gym reward profiling. Covers the basic gym env start, gym eval run, and gym eval profile workflow, repeated rollouts, materialized inputs, rollout JSONL artifacts, task and rollout identity, output inspection, partial…

updated
occupation
unclassified
description

Use when creating, validating, or documenting Nemo Gym pivot datasets from rollout, trajectory, chat-completion, Responses API, or tool-call artifacts. Covers Gym Responses-style row conversion, reconstructing model calls from flattened rollout output,…

updated
occupation
Software Developers
description

Guide for adding a new benchmark or training environment to NeMo-Gym. Use when the user asks to add, create, or integrate a benchmark, evaluation, training environment, or resources server into NeMo-Gym. Also use when wrapping an existing 3rd-party benchmark…

updated
occupation
Software Developers
description

Maintain the NeMo Gym Fern docs site — add, update, move, or remove pages under fern/. Use for any documentation change. Triggered by: "edit docs", "add doc page", "update docs", "rename page", "fix broken link", "add redirect", "preview docs", "publish…

updated
occupation
Software Developers
description

Manage stacked branches and pull requests with the gh-stack GitHub CLI extension. Use when the user wants to create, push, rebase, sync, navigate, or view stacks of dependent PRs. Triggers on tasks involving stacked diffs, dependent pull requests, branch…

updated
occupation
Software Developers
description

Use when analyzing NeMo Gym benchmark rollouts for BLADE-style reports, writing benchmark methodology notes, checking whether a benchmark is BLADE-ready, comparing model runs, or explaining why a benchmark report passed, failed, or changed. Covers aggregate…

updated
occupation
Software Developers
description

Use when debugging a Nemo Gym run or reward profiling job. Covers rollout collection failures, empty or partial JSONL outputs, stale materialized inputs, verifier/schema errors, Ray or Slurm issues, vLLM readiness, judge failures, tool/sandbox failures, cache…

updated
Showing 7 of 7 collected skills.