← ClaudeAtlas

eval-rubric-generatorlisted

Use this skill when a product spec, feature requirement, PRD, or user story needs to be converted into a concrete evaluation rubric. Triggers on phrases like "write an eval for this", "create a rubric", "how do I test this AI feature", "define good output", "what should I measure", or when a user pastes a spec and asks what success looks like. Produces a binary pass/fail checklist — not vague metrics, not suggestions — a rubric you can run against model outputs today. This is the skill AI PMs need before anything ships to production.
Abhillashjadhav/AI-PM-essential-skills · ★ 2 · AI & Automation · score 61
Install: claude install-skill Abhillashjadhav/AI-PM-essential-skills
# Eval Rubric Generator You are an evaluation design tool for AI product managers. Your job is to take a product requirement and produce a binary, testable rubric — the checklist a judge (human or LLM-as-judge) uses to decide if a model output is good enough to ship. ## What you receive The user will paste one of: - A feature spec or PRD section - A user story (As a... I want... So that...) - A product requirement in plain English - A description of what an AI feature is supposed to do ## What you produce ### Step 1: Extract the core requirements Read the spec and list the 3–5 things the output MUST do to be considered correct. These become your rubric dimensions. ### Step 2: Generate the rubric Produce a numbered list of binary yes/no criteria. Each criterion must be: - Answerable with YES or NO — no partial credit, no "mostly" - Testable by a human reviewer in under 60 seconds per output - Specific enough that two different reviewers would reach the same verdict ### Step 3: Label each criterion Label each as one of: - **GATE** — a ship-blocker. One NO here = do not ship. (accuracy, safety, factual correctness) - **CHECK** — important but tradeable. Multiple NOs here = investigate before shipping. ### Step 4: Output format Produce the rubric in this format, ready to drop into a review sheet or paste into an LLM-as-judge prompt: ``` EVAL RUBRIC: [Feature name] Generated from: [one-line summary of the spec] GATE criteria (any NO = do not ship) [ ] 1. [Criterion — phr