meta-eval

Diagnose evaluation scenarios and route users to the appropriate OpenJudge evaluation workflow.

809|65|Updated Jul 8, 2025
One-click install
npx skills add https://github.com/agentscope-ai/OpenJudge --skill meta-eval
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meta-eval
Source: https://github.com/agentscope-ai/OpenJudge/tree/main/skills/eval_pipeline/00-meta-eval
Command: npx skills add https://github.com/agentscope-ai/OpenJudge --skill meta-eval

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams building LLM or agent applications often don't know where to start with evaluation — they may have traces, prompts, RAG pipelines, or nothing at all. This Skill acts as a triage router that diagnoses the user's situation and points them to the correct evaluation workflow instead of letting them guess.

Core Features & Use Cases

  • Structured Diagnosis: Asks four diagnostic questions covering data form, label availability, stakes, and domain knowledge to classify the user's scenario.
  • Triage Routing: Maps the diagnosed situation to one of eight sub-workflows (eval design, metric design, human alignment, eval report, RAG eval, prompt regression, red teaming, or bootstrap) via a triage table.
  • Precondition Enforcement: Blocks premature routing — for example, refusing prompt-regression before paired baseline/candidate outputs exist, and refusing to call anything production-ready without ≥50 human labels and calibration.
  • Use Case: A user says "I have production agent logs but no labels — how do I evaluate quality?" The Skill diagnoses data=traces, labels=none, and routes them to the eval-design workflow, then outlines the path to metric design and later human calibration.

Quick Start

Ask the assistant to help you figure out how to start evaluating your LLM application and answer its four diagnostic questions about your data, labels, stakes, and domain knowledge.

Frequently Asked Questions about meta-eval

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

FAQPage Schema
How do I start evaluating an LLM application with no test data?

When you have no data or labels, the router directs you to the bootstrap workflow, which uses zero-shot rubric generation to produce a v0 grader in about 30 minutes. It then lays out a roadmap for collecting human labels and calibrating later.

How do I evaluate agent traces or production logs?

If you have agent traces or production logs, the router sends you to the eval-design workflow, which extracts evaluation dimensions from traces and builds a dataset in OpenJudge format. Metric design and grader selection come after the dataset exists.

When can I compare two prompts with A/B testing?

Prompt regression comparison requires paired outputs: both the baseline and candidate prompts must already be run on shared queries. The router explicitly blocks routing to prompt-regression until those paired outputs exist, since comparing unrun prompts is impossible.

Can an LLM judge be production-ready without human labels?

No. The skill enforces that production or regulated stakes require at least 50 human labels plus a human-alignment calibration step measuring TPR/TNR and kappa agreement before any ship decision. Unlabeled systems are never considered production-ready.

What evaluation scenarios does this router not cover?

It does not run evaluations itself, and it excludes continuous production monitoring (handled by MLOps tools like Arize or Braintrust), versioned public benchmark leaderboards, and real-time signal systems embedded in agent harnesses.