advanced-evaluation

Implements LLM-as-judge evaluation pipelines with bias mitigation, rubric generation, and metric selection.

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

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 & Pairwise Comparison: Choose the right evaluation approach based on whether objective ground truth exists, with structured prompt templates for each. - Bias Mitigation: Apply position swapping, length normalization, cross-model evaluation, and evidence requirements to counter systematic judge biases. - Rubric Generation & Metric Selection: Generate domain-specific scoring rubrics that reduce evaluation variance by 40-60%, and select appropriate statistical metrics (Spearman's rho, Cohen's kappa, F1) to validate against human judgments. - Use Case: When A/B testing two prompt variants, run pairwise comparisons with position swapping to get a consistent winner with calibrated confidence instead of a single biased judgment. ## Quick Start Ask the AI to compare two model responses to a prompt using pairwise comparison with position-swap bias mitigation and return a winner with confidence score.

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

Choose direct scoring when objective criteria exist (accuracy, instruction following) and pairwise comparison for subjective preferences (tone, style). Structure prompts with explicit criteria, require evidence-based justification before scores, and return structured JSON output.

How to mitigate position bias in pairwise LLM comparison?▼

Run the comparison twice with swapped response positions, then check consistency. If both passes agree on the same 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 format compliance. Use pairwise comparison for subjective quality judgments like tone, persuasiveness, or creativity, where it achieves higher agreement with human judges.

What metrics validate automated evaluation against human judgments?▼

Use Spearman's rho or Kendall's tau for ordinal scales, Cohen's kappa for categorical judgments, and precision/recall/F1 for binary classification. Track position consistency above 0.9 and keep length-score correlation below 0.2 to detect bias.

Why do LLM judges give inconsistent evaluation scores?▼

Inconsistency comes from position bias, length bias, overloaded criteria measuring multiple things, and missing edge-case guidance. Fix this with position swapping, explicit anti-length instructions, one measurable aspect per criterion, and detailed rubrics with edge cases.

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

LLM judges exhibit self-enhancement bias toward their own outputs, sensitivity to prompt wording causing 10-20% score swings, and rubric drift over time. Mitigate with cross-model evaluation, version-controlled prompts, and periodic rubric recalibration against human examples.