ai-feature-eval-harness

Designs dataset-backed evaluation plans for model-backed product features with measurable pass thresholds.

6|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/Mozurok/fhorja.dev --skill ai-feature-eval-harness-mozurok
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ai-feature-eval-harness
Source: https://github.com/Mozurok/fhorja.dev/tree/main/.claude/skills/ai-feature-eval-harness
Command: npx skills add https://github.com/Mozurok/fhorja.dev --skill ai-feature-eval-harness-mozurok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI features that ship on vibes have no held-out dataset, no pass threshold, and no way to detect quality regressions until users complain. This Skill designs a repeatable, dataset-backed evaluation plan for any model-backed product feature before and after it ships. ## Core Features & Use Cases - Measurable Success Criteria: Converts vague goals like "good answers" into concrete targets such as extraction F1 >= 0.9, refusal rate <= 1%, or p95 latency bounds. - Eval Dataset Specification: Defines the held-out labeled set including size, sourcing (production samples, synthetic, adversarial), label schema, and a split with no train/eval leakage. - Tiered Grading Strategy: Assigns code-based grading (exact match, F1, regex) to objective criteria and LLM-as-judge with a locked rubric only to nuanced criteria, then sets a suite-level pass threshold and regression rule persisted as AI_EVAL_PLAN.md. - Use Case: Before shipping an LLM-powered summarization feature, use this Skill to produce an eval plan with a 200-case gold set, per-criterion grading tiers, and a pass threshold wired into the slice's exit criteria. ## Quick Start Ask the AI to design an evaluation plan for your model-backed feature, defining measurable success criteria, a held-out labeled dataset, grading methods, and a pass threshold saved as AI_EVAL_PLAN.md.

Frequently Asked Questions about ai-feature-eval-harness

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

FAQPage Schema
How do I create an evaluation plan for an LLM feature?▼

Define measurable success criteria, specify a held-out labeled dataset with sourcing and label schema, assign a grading method per criterion, and set a pass threshold. This Skill walks those steps and persists the result as AI_EVAL_PLAN.md.

When should I use LLM-as-judge versus code-based grading?▼

Use code-based grading (exact match, regex, F1, BLEU) for objective criteria a program can score. Reserve LLM-as-judge with a locked rubric for nuanced criteria, since it is slower, costlier, and itself needs rubric governance.

What is the difference between an eval plan and deterministic tests?▼

Deterministic tests verify fixed behavior of pure functions and CRUD logic. An eval plan scores non-deterministic model outputs against a held-out labeled dataset with statistical pass thresholds, which functional tests cannot do.

Can I build an eval dataset if no labeled data exists yet?▼

Yes. The plan specifies how to bootstrap the first version: sourcing from production samples, synthetic generation, and adversarial edge cases, plus a minimum viable size and labeling approach.

When should I not use an AI feature eval harness?▼

Skip it when the feature has no model-backed output anywhere in its path; purely deterministic behavior belongs in conventional test strategy. It also does not build or run the harness, only plans the evaluation.