eval-engineer

Designs evaluation suites and scoring methods for AI workflows.

Updated Jul 12, 2026
One-click install
npx skills add https://github.com/sumitake/agent-collab --skill eval-engineer-sumitake
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eval-engineer
Source: https://github.com/sumitake/agent-collab/tree/main/plugins/agent-collab/skills/eval-engineer
Command: npx skills add https://github.com/sumitake/agent-collab --skill eval-engineer-sumitake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams shipping prompts, retrieval pipelines, or agent workflows often have no structured way to tell whether a change made the system better or worse. This Skill designs evaluation suites that give a defensible answer to "is this good enough to ship" grounded in scenarios that resemble real usage. ## Core Features & Use Cases - Scenario Design: Builds test scenarios from real failure modes and logged incidents rather than synthetic examples, covering multi-step agentic workflows and retrieval grounding. - Scoring Method Selection: Chooses among deterministic assertions, rubric-based grading, and model-graded judgment for each scenario class, with judge consistency and calibration checks. - Regression Strategy: Sets thresholds that catch real degradation without false alarms, and reports cost and latency alongside quality. - Use Case: Before shipping a new retrieval pipeline, use this Skill to produce a prioritized scenario matrix with metrics per class, a regression threshold, and an explicit statement of what still requires live or shadow validation. ## Quick Start Ask the agent to design an eval suite for your prompt or agent workflow, including failure-mode scenarios, scoring methods, and regression thresholds.

Frequently Asked Questions about eval-engineer

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

FAQPage Schema
How do I design an eval suite for an AI workflow?▼

Start by identifying the decision the evaluation supports, then enumerate production failure modes ranked by damage and turn the worst ones into test scenarios. Attach the cheapest trustworthy scoring method to each scenario class and set regression thresholds.

How to evaluate a retrieval-augmented generation pipeline?▼

Measure whether retrieved context actually supports the final answer separately from whether the answer sounds plausible. Combine deterministic grounding checks with rubric-based grading, and pull test cases from real usage rather than synthetic examples.

When should I use model-graded judgment versus deterministic assertions?▼

Use deterministic assertions like schema validity or exact match when the claim is mechanically checkable. Reserve model-graded judgment for open-ended quality claims, and verify the judge produces stable scores across repeated runs before trusting it.

What are the limitations of offline evaluation for AI agents?▼

Offline evaluation cannot reveal behavior that only appears under live traffic, real user distribution, or monitored rollouts. A sound evaluation plan states explicitly what it cannot verify and what still requires live or shadow validation.

Why does my eval suite pass but the workflow still fails in production?▼

Common causes are unrepresentative test scenarios, proxy metrics that diverge from the real outcome, or mislabeled dataset cases. Check dataset quality and scenario coverage before blaming the workflow for a low score.