eval

Compares Model A and Model B outputs on Marlin V3 across multiple turns with traceable eval-state.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/MinhOmega/marlin-skill --skill eval-minhomega
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eval
Source: https://github.com/MinhOmega/marlin-skill/tree/main/.claude/skills/eval
Command: npx skills add https://github.com/MinhOmega/marlin-skill --skill eval-minhomega

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides an end-to-end framework for evaluating competing model outputs (Model A and Model B) on Marlin V3 code across multiple turns, ensuring structured comparison, traceability, and reproducibility.

Core Features & Use Cases

  • Stateful, turn-based evaluation with A/B pair analysis, including eval-state management and cacheable context.
  • Independent A and B evaluation paths with axis-based scoring, trace reading, and justification across turns.
  • Use cases include validating prompt engineering changes, comparing code review suggestions, and surfacing regressions across model iterations.

Quick Start

Start an evaluation session by invoking /eval with repo, PR, and turn parameters to begin recording turns.

Frequently Asked Questions about eval

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

FAQPage Schema
How do I run structured A/B evaluation for code generation models?

Structured A/B evaluation compares Model A and Model B outputs across multiple turns using axis-based scoring. It maintains a reproducible eval-state with trace reading and baseline reference files for auditable cross-model comparisons.

What is turn-based code evaluation and how does it work with model traces?

Turn-based code evaluation analyzes model outputs sequentially across 13 axes, reading injected traces to score and justify responses. It maintains a cacheable context and eval-state to ensure strict reproducibility throughout the session.

How do I start an A/B evaluation session for Marlin V3 code?

Start an A/B evaluation session by invoking the eval command with repo, PR, and turn parameters. This initializes the eval-state and begins recording the independent A and B evaluation paths for comparison.

Can I use this evaluation framework to validate prompt engineering changes?

Yes, validating prompt engineering changes is a primary use case. The framework compares code review suggestions across model iterations, surfacing regressions by evaluating independent A and B paths with traceable, axis-based scoring.

Does the framework support reproducible cross-model evaluation with guardrails?

The framework satisfies strict requirements for reproducibility, traceability, and guardrails in cross-model evaluation. It uses baseline reference files and eval-state management to ensure all A/B pair analysis remains fully auditable.

What are the limitations of using axis-based scoring for code review comparisons?

Axis-based scoring across 13 dimensions requires baseline reference files and injected traces to function correctly. Without proper eval-state management and cacheable context, maintaining strict reproducibility across multiple turns becomes challenging.