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…
NVIDIA-NeMo/Gym
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 12
- GitHub stars
- 1,302
- GitHub forks
- 429
Install with an AI assistant
Copy this prompt into the AI assistant you're using.
Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/NVIDIA-NeMo/Gym.Loading the repository README…
Skills in this repository
Showing 12 of 12 collected skills.
Guide for adding or updating an agent harness in NeMo-Gym: a CLI or SDK agent runtime (for example Hermes, Pi, Codex, OpenCode, or an agent framework) wrapped as an Agent Server adapter that runs through Gym's Environment Server and agent sessions. Use when…
NeMo Gym pull-request review rubric used by the formal /review service, including automatic reviews.
Inspect and prepare NVIDIA-NeMo/Gym pull requests by reviewing relevant file history, selecting repository-specific local and CI checks, diagnosing missing or failed checks, and choosing current type, area, and state labels. Use for PR readiness, check…
Publish a NeMo Gym release by running the "Build, validate, and release NeMo-Gym" workflow (release.yaml) as a dry run, checking that the wheel installs, then publishing to PyPI and GitHub and verifying the result. Use when asked to release, publish, cut, or…
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…
Write and review user-focused NeMo Gym release notes and README news entries. Use when drafting, editing, prioritizing, or validating a release summary, release-note section, changelog highlights, or release announcement.
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…
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…
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,…
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…
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…