nemo-evaluator-sdk

Evaluates LLMs across 100+ benchmarks with containerized multi-backend execution on Docker, Slurm, and cloud.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/Clay-HHK/claude-skills --skill nemo-evaluator-sdk-clay-hhk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nemo-evaluator-sdk
Source: https://github.com/Clay-HHK/claude-skills/tree/main/nemo-evaluator
Command: npx skills add https://github.com/Clay-HHK/claude-skills --skill nemo-evaluator-sdk-clay-hhk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires nemo-evaluator-launcher, docker, and includes references (resource) components.

What problem does it solve? Running LLM benchmarks consistently across different harnesses, environments, and infrastructure is fragmented and hard to reproduce. This Skill provides a unified workflow for evaluating models against 100+ benchmarks from 18+ harnesses (MMLU, HumanEval, GSM8K, safety, VLM) using NVIDIA's NeMo Evaluator with containerized, reproducible execution. ## Core Features & Use Cases - Multi-benchmark evaluation: Run academic, coding, safety, function-calling, and vision-language benchmarks against any OpenAI-compatible endpoint (vLLM, TRT-LLM, NVIDIA NIM). - Multi-backend execution: Execute evaluations locally with Docker, on Slurm HPC clusters with model deployment, or on Lepton cloud, with job status tracking and result export to MLflow, W&B, or JSON. - Model comparison: Benchmark multiple models on identical tasks using Hydra config overrides, then export and compare results. - Use Case: A research team wants to compare Llama 3.1 8B and Mistral 7B on MMLU-Pro, GSM8K, and IFEval. They create one base config, run two evaluations with model overrides, and export both result sets to MLflow for side-by-side comparison. ## Quick Start Ask the AI to evaluate a model on standard benchmarks like MMLU and GSM8K using NeMo Evaluator with a local Docker execution config pointing at your OpenAI-compatible endpoint.

Frequently Asked Questions about nemo-evaluator-sdk

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

FAQPage Schema
How do I evaluate an LLM on MMLU and GSM8K benchmarks?▼

Install nemo-evaluator-launcher, create a Hydra config specifying your model endpoint and task list (mmlu_pro, gsm8k_cot_instruct), then run nemo-evaluator-launcher run with your config. Results are written to the configured output directory as results.yml files.

NeMo Evaluator vs lm-evaluation-harness for LLM benchmarking?▼

NeMo Evaluator aggregates 18+ harnesses including lm-evaluation-harness into one containerized platform with Slurm and cloud execution. Use lm-evaluation-harness alone for simpler quick local evaluation; use NeMo Evaluator for reproducible multi-harness or HPC-scale runs.

Can I run LLM evaluations on a Slurm HPC cluster?▼

Yes, configure the slurm execution backend with hostname, account, partition, and walltime, optionally adding a vLLM or SGLang deployment section. The launcher submits jobs via SSH and sbatch, and you monitor status with nemo-evaluator-launcher status.

Does NeMo Evaluator work with vLLM or self-hosted endpoints?▼

Yes, any OpenAI-compatible endpoint works by setting target.api_endpoint.url to your server, such as http://localhost:8000/v1/chat/completions. It supports chat, completions, vlm, and embedding endpoint types, with no API key needed for local servers.

Why does my evaluation task fail with a missing environment variable error?▼

Some tasks like gpqa_diamond require HF_TOKEN, and judge-based tasks need JUDGE_API_KEY. Declare them in the task's env_vars section mapping the required variable name to an environment variable set on your host.

How do I test an evaluation config quickly before a full run?▼

Use the --dry-run flag to validate configuration without execution, or override limit_samples via CLI with -o +evaluation.nemo_evaluator_config.config.params.limit_samples=10 to run only a few samples per task.