agentleFS
vikas8520-codervikas8520-coder/nerve/skills/cli-eval/SKILL.md

cli-eval

Skill0 starsChanged 3 months agoMITView on GitHub

Create and run evaluation suites, watch live benchmark progress, view scorecards, compare model performance, and integrate eval runs with CI workflows from the CLI.

  • Installs packages

3 other projects use a version of this, 3 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 2 are common, 0 are distinctive, and 0 are very specific to this project.

  • 2

    Common

    Most of the 3 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Create and run evaluation suites, watch live benchmark progress, view scorecards, compare model performance, and integrate eval runs with …

    line 9
  2. Common:

    Run the same suite against multiple models and compare:

    line 241

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- generated by src/lib/agentSkills/generator.ts; manual edits will be overwritten -->

Overview

Create and run evaluation suites, watch live benchmark progress, view scorecards, compare model performance, and integrate eval runs with CI workflows from the CLI.

Quick install

npm install -g nerve   # or: npx nerve
nerve --version

Subcommands

eval

Example:

nerve eval

eval suites

Example:

nerve eval suites

eval list

Example:

nerve eval list

eval get <suiteId>

Example:

nerve eval get <suiteId>

eval create

Flags:

  • --file <path>

Example:

nerve eval create

eval run <suiteId>

Flags:

  • -m, --model <id>
  • --combo <name>
  • --concurrency <n>
  • --tag <tag>
  • --watch

Example:

nerve eval run <suiteId>

eval list

Flags:

  • --suite <id>
  • --status <s>
  • --since <ts>
  • --limit <n>

Example:

nerve eval list

eval get <runId>

Example:

nerve eval get <runId>

eval results <runId>

Flags:

  • --failed

Example:

nerve eval results <runId>

eval cancel <runId>

Flags:

  • --yes

Example:

nerve eval cancel <runId>

eval scorecard <runId>

Example:

nerve eval scorecard <runId>

simulate [prompt]

Flags:

  • --file <path>
  • -m, --model <id>
  • --combo <name>
  • --reasoning-effort <level>
  • --thinking-budget <n>
  • --explain

Example:

nerve simulate [prompt]
<!-- skill:custom-start --><!-- Migrated from skills/nerve-cli-eval/SKILL.md (preserved curated content) -->

Nerve — CLI Evals

Requires the nerve CLI. See CLI entry-point skill for install + global flags.

What are evals?

Evals are automated test suites that score LLM outputs against expected answers or rubrics. Nerve stores suites and run results in its local database.

Eval suites

nerve eval suites list                       # List all eval suites
nerve eval suites list --json                # JSON output

nerve eval suites get <suiteId>              # Full suite definition

Create a suite

nerve eval suites create \
  --name "code-quality" \
  --rubric "exact-match" \
  --samples-file ./samples.jsonl                 # JSONL: {input, expected_output}

Rubric options: exact-match, contains, llm-judge, regex.

--samples-file format (one JSON object per line):

{"input": "What is 2+2?", "expected_output": "4"}
{"input": "Translate 'hello' to Spanish", "expected_output": "hola"}

Run an eval

nerve eval suites run <suiteId> \
  --model claude-sonnet-4-6                      # Run suite against a specific model

nerve eval suites run <suiteId> \
  --model gpt-4o \
  --watch                                        # Live TUI progress (EvalWatch)

The run is asynchronous. Use --watch for a live terminal dashboard or poll manually:

RUN_ID=$(nerve eval suites run <suiteId> --model claude-sonnet-4-6 --output json | jq -r '.id')
nerve eval get $RUN_ID

Manage runs

nerve eval list                              # List all eval runs
nerve eval list --json

nerve eval get <runId>                       # Run details (status, model, score)
nerve eval results <runId>                   # Per-sample results
nerve eval scorecard <runId>                 # Full scorecard with pass/fail per sample
nerve eval cancel <runId>                    # Cancel a running eval

Scorecard output

nerve eval scorecard <runId> --output json

Response fields per sample:

{
  "id": "sample-1",
  "score": 0.95,
  "passed": true,
  "input": "What is 2+2?",
  "output": "4",
  "expected": "4"
}

Comparing models

Run the same suite against multiple models and compare:

for MODEL in claude-sonnet-4-6 gpt-4o gemini-2.0-flash; do
  nerve eval suites run $SUITE_ID --model $MODEL --output json | jq '{model: .model, score: .score}'
done

CI integration

# Run and fail CI if score drops below threshold
SCORE=$(nerve eval suites run $SUITE_ID --model claude-sonnet-4-6 --output json | jq -r '.score')
python3 -c "import sys; score=float('$SCORE'); sys.exit(0 if score >= 0.90 else 1)"

Errors

  • suites create fails with invalid rubric → use one of: exact-match, contains, llm-judge, regex
  • suites run returns model not found → verify model ID with nerve models --search <name>
  • eval get shows status: failed → check nerve logs --search eval for error details
  • scorecard returns empty results → the run may still be running; poll nerve eval get <runId> until status is completed
<!-- skill:custom-end -->

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.