Individual skill
comparative-evaluation
A/B testing, side-by-side comparison, and preference ranking for AI outputs.
gemini-extension/evaluation/skills/comparative-evaluation/SKILL.md
Source commit f41b650435b62dec6d5b1dc3598ac4679f8b7ae7
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 203
- Repository last updated
- Jun 9, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,460 bytes
Read excerpt
# 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: