Agent skill · DevOps & Cloud

nemo-evaluator-sdk

Evaluates LLMs across 100+ benchmarks from 18+ harnesses (MMLU, HumanEval, GSM8K, safety, VLM) with multi-backend execution. Use when needing scalable evaluation on local Docker, Slurm HPC, or cloud platforms. NVIDIA's enterprise-grade platform with container-first architecture for reproducible benchmarking.

Orchestra-Researchgithub.com/Orchestra-ResearchGitHub ↗
claude-codecodexMIT
Install
npx skills add Orchestra-Research/AI-Research-SKILLs --skill nemo-evaluator --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 5
SKILL.md size: 12 KB
Bundled scripts: none
Version: 1.0.0
Declared author: Orchestra Research
Requires: [nemo-evaluator-launcher>=0.1.25, docker]
Path: 11-evaluation/nemo-evaluator/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 11,391
Language: TeX
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# NeMo Evaluator SDK - Enterprise LLM Benchmarking ## Quick Start NeMo Evaluator SDK evaluates LLMs across 100+ benchmarks from 18+ harnesses using containerized, reproducible evaluation with multi-backend execution (local Docker, Slurm HPC, Lepton cloud). **Installation**: ```bash pip install nemo-evaluator-launcher ``` **Set API key and run evaluation**: ```bash export NGC_API_KEY=nvapi-your-key-here # Create minimal config cat > config.yaml << 'EOF' defaults: - execution: local - deployment: none - _self_ execution: output_dir: ./results target: api_endpoint: model_id: meta/llama-3.1-8b-instruct url: https://integrate.api.nvidia.com/v1/chat/completions api_key_name: NGC_API_KEY evaluation: tasks: - name: ifeval EOF # Run evaluation nemo-evaluator-launcher run --config-dir . --config-name config ``` **View available tasks**: ```bash nemo-evaluator-launcher ls tasks ``` ## Common Workflows ### Workflow 1: Evaluate Model on Standard Benchmarks Run core academic benchmarks (MMLU, GSM8K, IFEval) on any OpenAI-compatible endpoint. **Checklist**: ``` Standard Evaluation: - [ ] Step 1: Configure API endpoint - [ ] Step 2: Select benchmarks - [ ] Step 3: Run evaluation - [ ] Step 4: Chec

What's inside
Steps it walks through
  1. Quick Start
  2. Common Workflows
  3. Workflow 1: Evaluate Model on Standard Benchmarks
  4. Workflow 2: Run Evaluation on Slurm HPC Cluster
  5. Workflow 3: Compare Multiple Models
  6. Workflow 4: Safety and Vision-Language Evaluation
  7. When to Use vs Alternatives
  8. Supported Harnesses and Tasks
  9. Common Issues
  10. CLI Reference
  11. Configuration Override Examples
  12. Python API Usage
  13. Advanced Topics
  14. Requirements
Ships with 4 files
  • references/adapter-system.md
  • references/configuration.md
  • references/custom-benchmarks.md
  • references/execution-backends.md
Commands it runs
pip install nemo-evaluator-launcher
export NGC_API_KEY=nvapi-your-key-here
Create minimal config
cat > config.yaml << 'EOF'
Run evaluation
nemo-evaluator-launcher run --config-dir . --config-name config
nemo-evaluator-launcher ls tasks
Run with config file
nemo-evaluator-launcher run \
Override output directory
More from AI-Research-SKILLs
All skills →
About this skill
What does the nemo-evaluator-sdk skill do?

Evaluates LLMs across 100+ benchmarks from 18+ harnesses (MMLU, HumanEval, GSM8K, safety, VLM) with multi-backend execution. Use when needing scalable evaluation on local Docker, Slurm HPC, or cloud platforms. NVIDIA's enterprise-grade platform with container-first architecture for reproducible benchmarking.

How do I install it?

Run `npx skills add Orchestra-Research/AI-Research-SKILLs --skill nemo-evaluator --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From Orchestra-Research/AI-Research-SKILLs, a repository with 11,391 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going