Skip to main content

The fastest path: multivon-eval bootstrap

Don’t know what to eval for your specific LLM product? Describe it and hand over a few sample traces. multivon-eval bootstrap proposes a tuned suite in a few minutes.
Returns five files: eval_suite.py (runnable), seed_cases.jsonl (30 adversarial cases), thresholds.yaml (calibrated from your traces), DISCOVERY_REPORT.md (an eval design review), and prompt_baseline.json (a prompt call-site baseline written at the repo root for staleness tracking). Cost: ~$0.12 default, or free with --judge-provider ollama. Full walkthrough → Run it fully offline with a local judge:

Wire it into Claude Code with install-skills

Symlinks three bundled Claude Code skills into ~/.claude/skills/. From that point on:
  • Say “add evals to this project” → Claude Code auto-invokes /eval-bootstrap.
  • Ask “why did multivon recommend Faithfulness?”/eval-explain answers.
  • Before /ship on a PR that touches prompts or tool defs → /eval-audit runs only the cases that exercise the changed surface and gates the PR.
See /guides/install-skills and /skills/index.

Or try the canned demo

Runs a self-contained customer-support eval; the deterministic tier needs no API key. If ANTHROPIC_API_KEY, OPENAI_API_KEY, or a local endpoint is detected, LLM-judge evaluators are added automatically.

Install

For LLM-judge evaluators, add your API key:

The fastest start: plain-English checks

Don’t know which evaluator to use? Write what you want in English:
add_check auto-generates yes/no questions from your criterion and scores with QAG. When you want to pin the exact questions, graduate to CustomRubric.

Option A — Generate cases from your docs

No labeled data? Point generate_from_file() at any text file and get eval cases immediately.

Option B — Define cases manually

Load cases from a file

cases.jsonl

Run in parallel

Block CI on regression

Use inside pytest

Drop a suite into an existing pytest test file — no special plugin required.
Run it like any other test: pytest tests/test_evals.py. Pair with fail_threshold if you prefer an exit-code approach over an assertion.

Track experiments across runs

Next steps

Plain-English checks

Write criteria in English — SDK generates the questions

Synthetic dataset generation

Generate eval cases from your docs — no labels required

LLM judge evaluators

Faithfulness, hallucination, relevance, and more

Agent evaluation

Tool call accuracy and plan quality

Experiment tracking

Compare runs, catch regressions

CI/CD integration

Run evals as a quality gate

Prompt-drift staleness

Know which prompts changed since your cases were authored

Persona simulation

Drive adaptive multi-turn conversations with synthetic personas

Install Claude Code skills

Auto-invoke bootstrap, audit, and explain skills