add-benchmark

Integrate new NeMo-Gym benchmarks with JSONL data and verify() rewards.

Updated May 23, 2026
One-click install
npx skills add https://github.com/yo-steven/skills-exploration-20260522 --skill add-benchmark-yo-steven
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-benchmark
Source: https://github.com/yo-steven/skills-exploration-20260522/tree/main/skills/NeMo-Gym/add-benchmark
Command: npx skills add https://github.com/yo-steven/skills-exploration-20260522 --skill add-benchmark-yo-steven

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the guesswork and repetitive setup required to add a new benchmark or training/evaluation environment to NeMo-Gym, especially when you must wire data, a resources server, an agent, and verification logic into one working workflow.

Core Features & Use Cases

  • Benchmark integration workflow: Covers adding either a native benchmark (resources server implements verify() and reward logic) or an external benchmark (wraps an existing library at the agent layer) end to end.
  • Data + verifier schema guidance: Shows how to convert datasets into Gym JSONL with responses_create_params.input and verifier_metadata, including generating example.jsonl, validating data, and preparing train/validation via GitLab registry.
  • Robust verify() implementation rules: Provides guardrails for safe reward computation (binary rewards), concurrency control, graceful failure on empty/bad outputs, and patterns for subprocess/ray execution and external tool auto-install.
  • Config and testing checklist: Guides YAML wiring of resources server + agent pairing(s), required dataset fields, and how to run server tests and do smoke/e2e rollouts, followed by reward baselining/profiling.

Quick Start

Ask the assistant to guide you through adding a new benchmark by having it walk you through scaffolding a NeMo-Gym resources server, defining your JSONL data schema and verify() reward logic, wiring the YAML config, and running tests plus a baseline reward profile.

Frequently Asked Questions about add-benchmark

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new benchmark to NeMo-Gym?

To add a benchmark to NeMo-Gym, choose native versus external integration, prepare JSONL datasets, implement verify() reward logic, wire YAML configuration, and run tests with smoke rollouts and reward profiling.

What is the difference between native and external benchmark integration?

Native benchmark integration implements verify() and reward logic directly in the resources server, while external benchmark integration wraps an existing library at the agent layer to handle evaluation externally.

How do I format JSONL datasets for NeMo-Gym benchmarks?

NeMo-Gym JSONL datasets require responses_create_params.input and verifier_metadata fields. You generate example.jsonl, validate the data, and prepare train/validation splits via GitLab registry.

What are the implementation rules for verify() reward computation in NeMo-Gym?

NeMo-Gym verify() reward computation requires binary reward returns, concurrency control, graceful failure handling for empty or bad outputs, and supports subprocess or ray execution with tool auto-install hooks.

How do I configure YAML for NeMo-Gym resources server and agent pairing?

YAML configuration for NeMo-Gym wires resources server and agent pairings, defines required dataset fields, and enables running server tests alongside smoke and end-to-end rollouts for workflow validation.

Do I need async HTTP for NeMo-Gym benchmark resources servers?

NeMo-Gym resources servers require aiohttp-based async HTTP patterns to handle concurrent requests correctly and maintain proper concurrency control during reward verification and workflow validation.