advanced-evaluation

Implements LLM-as-judge evaluation pipelines with bias mitigation, rubrics, and calibrated scoring.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/TECH-HY/SKILLS --skill advanced-evaluation-tech-hy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: advanced-evaluation
Source: https://github.com/TECH-HY/SKILLS/tree/main/skills/advanced-evaluation
Command: npx skills add https://github.com/TECH-HY/SKILLS --skill advanced-evaluation-tech-hy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Automated evaluation of LLM outputs is unreliable when judges suffer from position bias, length bias, and uncalibrated scoring. This Skill provides production-grade patterns for building LLM-as-judge systems that correlate with human judgment. ## Core Features & Use Cases - Direct Scoring & Pairwise Comparison: Implements both evaluation approaches with structured prompts, chain-of-thought justification, and position-swap protocols to neutralize bias. - Rubric Generation: Creates calibrated scoring rubrics with level descriptions, edge cases, and domain-specific terminology, reducing evaluation variance by 40-60%. - Bias Mitigation & Metric Selection: Provides frameworks for detecting position, length, and self-enhancement bias, plus guidance on choosing metrics like Spearman's ρ, Cohen's κ, and agreement rates. - Use Case: When A/B testing two prompt variants, use pairwise comparison with position swapping to determine which produces better responses, with confidence scores calibrated to cross-pass consistency. ## Quick Start Ask the agent to compare two model responses for a given prompt using pairwise comparison with position bias mitigation and return a JSON verdict with confidence.

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 for evaluating model outputs?

LLM-as-judge implementation uses either direct scoring for objective criteria or pairwise comparison for subjective preferences. Structure prompts with clear criteria, require evidence-based justification before scores, and output structured JSON with scores and reasoning.

How to mitigate position bias in pairwise LLM comparison?

Position bias is mitigated by running the comparison twice with swapped response positions. If both passes agree, average the confidences; if they disagree, return a TIE verdict with confidence capped at 0.5.

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 preferences like tone, style, or persuasiveness, where it achieves higher agreement with human judges.

What metrics should I use to validate an LLM judge against humans?

Metric selection depends on task structure: use recall, precision, and F1 for binary classification; Spearman's ρ or Kendall's τ for ordinal scales; and agreement rate with position consistency for pairwise preferences. Systematic disagreement patterns matter more than absolute agreement.

Why do LLM judges give inconsistent or unreliable scores?

Inconsistency usually stems from missing justification requirements, overloaded criteria measuring multiple things, or unmitigated biases like length and verbosity preference. Requiring chain-of-thought evidence before scoring improves reliability by 15-25%.

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

LLM judges exhibit self-enhancement bias when rating their own outputs and cannot fully replace human judgment for high-stakes decisions. For critical applications, use panels of multiple judge models or human-in-the-loop review for low-confidence cases.