Skip to content
Design
Skill

/comparative-evaluation

A/B testing, side-by-side comparison, and preference ranking for AI outputs.

BOOST
From plugin
ai-design-skills
18844 skills18 commands
Install
$ npx -y skills add owl-listener/ai-design-skills --skill comparative-evaluation --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/comparative-evaluation

Context preview

The summary Claude sees to decide when to auto-load this skill.

A/B testing, side-by-side comparison, and preference ranking for AI outputs.

SKILL.md

comparative-evaluation.SKILL.md
name: comparative-evaluation
description: A/B testing, side-by-side comparison, and preference ranking for AI outputs.

Comparative Evaluation

Absolute quality scores are useful but limited. Comparative evaluation — putting outputs side by side and asking which is better — often reveals quality differences that rubrics miss.

Comparison Methods

  • **A/B testing**: Show different users different versions and compare outcomes
  • **Side-by-side evaluation**: Show evaluators two outputs for the same input and ask which is better
  • **Preference ranking**: Show evaluators multiple outputs and rank them from best to worst
  • **Paired comparison**: Compare every pair of options to build a complete ranking
  • **Elo rating**: Use tournament-style comparisons to develop continuous quality scores

Designing A/B Tests for AI

A/B testing AI is different from A/B testing UI:

  • **Variance is high**: The same prompt can produce different outputs, so you need more samples
  • **Context matters**: The same change might help for one task and hurt for another
  • **Metrics lag**: AI quality changes may take time to show up in user behavior
  • **Interaction effects**: A change to one part of the conversation affects all subsequent parts

Design A/B tests with:

  • Sufficient sample sizes to account for output variance
  • Segmentation by task type and user experience level
  • Multiple metrics (don't optimise for one at the expense of others)
  • Guardrails to catch severe quality regressions quickly

Side-by-Side Evaluation Design

For human evaluation of AI outputs:

  • **Blind evaluation**: Evaluators shouldn't know which version is which
  • **Consistent inputs**: Compare outputs generated from the same input
  • **Structured criteria**: Give evaluators specific dimensions to compare on, not just "which is better"
  • **Multiple evaluators**: Use at least 3 evaluators per comparison for reliability
  • **Diverse inputs**: Test across a representative sample of real user inputs

When to Use Comparative vs. Absolute Evaluation

  • **Comparative**: Best for choosing between alternatives, detecting subtle quality differences, and model selection
  • **Absolute**: Best for measuring against a standard, tracking progress over time, and certification

Design Artefacts

  • A/B test design templates
  • Side-by-side evaluation protocols
  • Evaluator instructions and rubrics
  • Sample size calculators for AI experiments
  • Comparison result analysis frameworks
Read more
Ships withai-design-skills

Part of the Designer Skills suite. Install this collection and four more with one command in Claude Code: /plugin marketplace add Owl-Listener/designer-skills This repo still works on its own. The suite just gives everyone one front door.

Get the whole plugin

Other skills on ai-design-skills.