advanced-evaluation

Implements LLM-as-judge evaluation pipelines with direct scoring, pairwise comparison, and bias mitigation.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/whatswithavi/Ecchelon_project --skill advanced-evaluation-whatswithavi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: advanced-evaluation
Source: https://github.com/whatswithavi/Ecchelon_project/tree/main/.agent/skills/advanced-evaluation
Command: npx skills add https://github.com/whatswithavi/Ecchelon_project --skill advanced-evaluation-whatswithavi

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Automated evaluation of LLM outputs is unreliable when judges suffer from position bias, length bias, and inconsistent scoring. This Skill provides production-grade patterns for building LLM-as-judge systems that correlate with human judgment. ## Core Features & Use Cases - Direct Scoring: Rate single responses against weighted criteria with evidence-based justifications and calibrated scales. - Pairwise Comparison: Compare two responses with position-swapping protocols to detect and mitigate position bias. - Rubric Generation: Create domain-specific scoring rubrics with level descriptions, edge cases, and strictness calibration to reduce evaluation variance by 40-60%. - Use Case: When A/B testing a new prompt, use pairwise comparison with position swapping to determine which prompt version produces better responses, with confidence scores calibrated to position consistency. ## Quick Start Use the advanced-evaluation skill to compare these two model responses with position bias mitigation and tell me which one is better.

Frequently Asked Questions about advanced-evaluation

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

FAQPage Schema
How do I implement LLM-as-a-judge evaluation?▼

Build a pipeline with a criteria loader, primary scorer, bias mitigation layer, and confidence scoring. Use direct scoring for objective criteria like factual accuracy, and pairwise comparison for subjective preferences like tone and style.

How to mitigate position bias in pairwise LLM comparison?▼

Evaluate twice with swapped response positions, then check consistency. If both passes agree on the winner, average the confidences; if they disagree, return TIE with 0.5 confidence since position bias corrupted the result.

When should I use direct scoring vs pairwise comparison?▼

Use direct scoring when objective ground truth exists, such as factual accuracy or instruction following. Use pairwise comparison for subjective judgments like tone, style, or persuasiveness, where it achieves higher human-judge agreement.

What metrics validate automated evaluation against human judgment?▼

Use Spearman's rho or Kendall's tau for ordinal scales, Cohen's kappa for categorical judgments, and agreement rate for pairwise decisions. Values above 0.8 for Spearman's rho indicate strong correlation with human evaluators.

Why do LLM judges give inconsistent scores?▼

Inconsistency stems from position bias, length bias, missing rubrics, and prompt sensitivity where minor wording changes cause 10-20% score swings. Mitigate with position swapping, explicit length-neutrality instructions, detailed rubrics, and version-controlled prompts.

What are the limitations of LLM-as-judge evaluation?▼

LLM judges exhibit self-enhancement bias toward their own outputs, authority bias toward confident tone, and verbosity bias toward longer responses. Automated evaluation is only valuable when validated against human judgments with correlation monitoring.