write-ai-evals

Designs and runs evals for AI features using golden sets, rubrics, and LLM-as-judge grading.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/dineshrevunuru/SuperSkills --skill write-ai-evals-dineshrevunuru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-ai-evals
Source: https://github.com/dineshrevunuru/SuperSkills/tree/main/write-ai-evals
Command: npx skills add https://github.com/dineshrevunuru/SuperSkills --skill write-ai-evals-dineshrevunuru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI features ship without proof they work: prompts regress silently, models hallucinate prices or facts, and teams pick models from leaderboards instead of measuring cost-latency-quality on their own inputs. This Skill turns 'I tried it a few times, seems fine' into a rigorous eval practice with hard safety gates and regression detection. ## Core Features & Use Cases - Pre-design model capability assessment: Define the model's job in one sentence, bucket outputs into must-never-happen gates vs. quality dimensions, and choose model tiers and providers per layer (STT, reasoning, TTS) by measuring on your own real inputs. - Golden set construction and grading ladder: Build 20-50 row test sets from real user utterances with checkable expected outcomes, graded on a three-level ladder from deterministic code checks to calibrated LLM judges to human review. - Failure-mode taxonomy and production metrics: Name and count every failure, map it to a fix class (structural, provider swap, taxonomy, prompt, model tier), and instrument acceptance rate, regeneration rate, edit distance, and latency P95 after launch. - Use Case: Before shipping a voice shopping assistant, run a 20-query golden set with a hard gate of zero hallucinated products or prices, a binary rubric for grounded recommendations judged by a different model family, and a 100% pass bar on medicine-deferral rows. ## Quick Start Ask the AI to write an eval spec for your chatbot feature, including a golden set of 20 real user inputs, hard safety gates, and pass bars for each test suite.

Frequently Asked Questions about write-ai-evals

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

FAQPage Schema
How do I write evals for an LLM feature?

Start with a golden set of 20-50 real user inputs where every row has a checkable expected outcome like an exact enum value or must-refuse flag. Grade with deterministic code checks first, reserve LLM judges for judgment-shaped dimensions, and set a 100% pass bar on safety suites.

How do I choose which model to use for an AI feature?

Write the model's job in one sentence, then measure cost, latency, and quality on about ten of your own real inputs rather than trusting leaderboards. Pick the smallest tier that passes your golden set, and keep an environment-variable escape hatch to a larger model.

How do I use LLM-as-judge without unreliable scores?

Use binary pass/fail criteria instead of 1-10 scales, require a quoted-evidence field for every verdict, and give the judge the same source facts a human grader would see. Calibrate against about 20 human-graded samples before trusting it, and never delegate facts like prices or IDs to the judge.

When should I not use this eval skill?

Do not use it for designing user-facing failure UX like refusal copy or fallback screens, which belongs to design-ai-trust-and-failure-states. It also does not cover human-subject A/B testing with statistical significance or writing the production prompt itself.

Why does my AI feature still hallucinate after prompt fixes?

Prompt changes are the least durable fix class. Prefer structural fixes first: constrain outputs with closed enums and forced tool calls, have the server hydrate rendered facts from a verified catalog, and validate referenced facts post-generation so the failure channel no longer exists.