evaluation

Designs and audits self-evolution evaluations from real agent traces without ground truth.

1|Updated Aug 14, 2026
One-click install
npx skills add https://github.com/zhiyuan-zhang0206/Ava --skill evaluation-zhiyuan-zhang0206
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: evaluation
Source: https://github.com/zhiyuan-zhang0206/Ava/tree/main/ava_builtins/skills/ava-self-evolution/evaluation
Command: npx skills add https://github.com/zhiyuan-zhang0206/Ava --skill evaluation-zhiyuan-zhang0206

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Evaluating an AI skill is a measurement problem, not a test-suite problem: real run traces carry no ground truth, representative failure cases are naturally scarce, and scores only mean something as deltas between skill versions. This Skill defines the standard for building trustworthy evaluation case sets and auditing agent runs so scores reflect real behavior rather than leaked answers. ## Core Features & Use Cases - Eval Case Design: Selects cases from real traces that are strong (outcome hinges on the skill), diverse (cover distinct behavior areas), and representative (replay-safe, drawn from actual runs). - Batch Evaluation Execution: Spawns one fresh agent per case via evaluate.launch, gathers results asynchronously, and verifies replays against original tool profiles, excluding degenerate runs. - Anti-Cheat Trace Auditing: Audits what agents actually did against three leak surfaces — cluster memory, web search, and completed-task results — invalidating runs that touched a leak. - Use Case: After editing a skill, re-run a reviewed case set under old and new skill text, then audit each trace to confirm score deltas come from the skill change and not from an agent reading the original run's output. ## Quick Start Use the evaluation skill to build a strong, diverse, representative case set from my recent run traces and audit the batch results for leaks.

Frequently Asked Questions about evaluation

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

FAQPage Schema
How do I evaluate an AI agent skill without ground truth?▼

Evaluate comparatively: re-run the same case set under the old and edited skill text and read scores as deltas, not absolutes. Build cases from real traces and use rubric proxy signals like completion and efficiency rather than correctness labels.

What makes a good evaluation case for agent testing?▼

A good case is strong, diverse, and representative. The outcome must hinge on the skill under test, the set must cover distinct behavior areas, and each case must come from a real trace and be replay-safe with no side effects.

How do I prevent eval agents from cheating on benchmarks?▼

Audit three leak surfaces: shared cluster memory, web search, and access to the original run's artifacts. Isolate eval agents from each surface and invalidate any run whose trace shows it touched a leak, fixing the leak at its layer.

Why are representative evaluation cases hard to collect?▼

Real usage is long-tailed: most runs exercise a few common patterns while the failed or fumbled runs worth re-running are rare. This scarcity is structural, so treat it as a budget on how many measurements the loop can afford.

What are the limitations of trace-based agent evaluation?▼

Traces carry no answer key, so labelers only detect visible breakage and rubrics score proxy signals, not correctness. Some isolation layers remain staged: raw filesystem, database, and network containment await OS-level sandboxing.