evaluation

Evaluate agent performance across multi-step tool-using workflows with multi-dimensional rubrics.

Updated Apr 15, 2025
One-click install
npx skills add https://github.com/khrore/nix-config --skill evaluation-khrore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evaluation
Source: https://github.com/khrore/nix-config/tree/main/dotfiles/common/.config/opencode/skills/evaluation
Command: npx skills add https://github.com/khrore/nix-config --skill evaluation-khrore

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Evaluation of agent systems is hard because agents are non-deterministic, take multiple valid execution paths, and require multi-dimensional judgments rather than a single correctness metric. This skill provides methods and tooling to reliably measure agent quality, detect regressions, and validate context engineering and tool usage decisions so teams can ship safer, higher-quality agents.

Core Features & Use Cases

  • Multi-dimensional rubrics that score factual accuracy, completeness, citation accuracy, source quality, and tool efficiency with configurable weights.
  • LLM-as-judge prompts and human review guidance to scale evaluations while retaining human oversight for edge cases.
  • Test set design and complexity stratification for development and regression testing, plus a production monitoring sampler and pass-rate alerts to track quality over time.
  • Use cases: validating context strategies, comparing agent configurations, regression testing after model or prompt changes, and continuous monitoring of production agents.

Quick Start

Compare two agent configurations on the provided test set using the default multi-dimensional rubric and realistic token budgets.

Frequently Asked Questions about evaluation

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

FAQPage Schema
How do I evaluate agent performance for multi-step tool-using workflows?

To evaluate agent performance, you apply multi-dimensional rubrics that score factual accuracy, tool efficiency, and stateful workflow execution. This approach reliably measures non-deterministic agent quality by validating multi-step reasoning paths rather than relying on a single correctness metric.

What is the best way to monitor production agents and detect quality regressions?

The best way to monitor production agents is using a production monitoring sampler with pass-rate alerts. This setup tracks multi-step agent quality over time, enabling you to detect regressions after prompt or model changes and validate tool usage decisions continuously.

How does LLM-as-judge work for scaling agent evaluations?

LLM-as-judge works by applying configurable prompts to score agent outputs against multi-dimensional rubrics. It scales evaluations for retrieval and reasoning tasks while retaining human review guidance to oversee edge cases and validate citation accuracy.

Can I compare agent configurations using stratified test sets and token budget constraints?

Yes, you can compare agent configurations by applying complexity-stratified test sets and realistic token budget constraints. This process validates context engineering strategies and tool usage decisions across different agent setups to ensure safer deployments.

When do I need multi-dimensional rubrics instead of a single correctness metric for agent testing?

You need multi-dimensional rubrics when testing non-deterministic agents that take multiple valid execution paths. Rubrics score factual accuracy, completeness, and source quality, providing reliable regression testing for complex retrieval and multi-agent coordination scenarios.

Why does evaluating multi-agent coordination require complexity stratification in test sets?

Evaluating multi-agent coordination requires complexity stratification because agents take varied execution paths that single metrics cannot capture. Stratified test sets isolate reasoning and tool usage failures, ensuring accurate regression testing after context engineering changes.