forge-evals

Design, score, and run evals for LLM features with golden datasets and rubrics.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/f4rkh4d/forge-skill --skill forge-evals
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge-evals
Source: https://github.com/f4rkh4d/forge-skill/tree/main/skills/llm/forge-evals
Command: npx skills add https://github.com/f4rkh4d/forge-skill --skill forge-evals

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams stop relying on “looks good” prompts and instead measure whether an LLM feature improves or regresses after changes.

Core Features & Use Cases

  • Golden eval datasets: build and version 50+ held-out examples with clear intent and criteria.
  • Rubric-based scoring: score multiple criteria (not a single aggregate) for clearer signal and safer thresholds.
  • LLM-as-judge with calibration: use structured judge outputs and periodically calibrate against humans to avoid judge drift.
  • Regression + CI integration: re-run evals on prompt/model/retrieval changes and fail builds when quality drops.
  • Offline-to-online validation: use offline evals for prediction and validate with online A/B tests for real user outcomes.
  • Cost and latency budgets: include p50/p95 latency and per-call cost as dimensions alongside quality.

Quick Start

Ask an AI agent to help you design a rubric and create a 50-example held-out eval dataset for your LLM feature, then wire an eval runner into CI with ship/block thresholds and per-criterion reporting.

Frequently Asked Questions about forge-evals

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

FAQPage Schema
How do I set up regression testing for LLM applications in CI?

LLM regression testing in CI requires wiring an eval runner into your pipeline that re-runs held-out datasets on prompt or model changes and fails builds when quality drops below defined thresholds. You need a golden dataset and multi-criterion scoring to track per-example outcomes.

How does LLM-as-judge calibration work for evaluating model outputs?

LLM-as-judge calibration works by using structured judge outputs to score LLM behavior against a rubric, periodically validating against human reviews to prevent judge drift. This ensures automated scoring remains accurate and aligned with expected behavior criteria over time.

What is the best way to design a golden dataset for LLM evaluation?

The best way to design a golden eval dataset is to build and version 50 or more held-out examples with clear intent and expected behavior criteria. This dataset serves as the baseline for multi-criterion rubric scoring and regression detection during CI re-runs.

Can I track cost and latency budgets alongside quality in LLM evals?

You can track cost and latency budgets by including p50 and p95 latency along with per-call cost as evaluation dimensions alongside quality scores. This allows you to monitor production behavior constraints and ensure features stay within acceptable performance budgets.

How do I validate offline LLM evals with online A/B tests?

Validate offline LLM evals by using them to predict quality changes, then running online A/B tests to measure real user outcomes. This offline-to-online approach confirms that rubric scoring and held-out dataset results translate to actual production improvements.