Prompt to eval rubric
Skill alexzhu0/agent-ready-skills/skills/prompt-to-eval-rubric
Ten practical AI-agent skills for turning messy work into clear context, evals, reviews, and launch-ready artifacts.
npx -y skills add alexzhu0/agent-ready-skills --skill prompt-to-eval-rubricAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when converting prompts, system instructions, assistant behaviors, or policy requirements into eval rubrics with scoring criteria, test cases, assertions, and failure modes.
SKILL.md
1.5 KB, as published. Nobody here has run it
Prompt To Eval Rubric
Purpose
Turn desired model behavior into a reusable evaluation rubric.
Fit
- Use when prompt behavior must be evaluated repeatedly or compared across model/prompt versions.
- Do not use when the task is only rewriting the prompt and no evaluation criteria are needed.
Inputs
- Prompt, system instruction, policy, desired behavior, or bad output.
- User goals, safety requirements, and known failure modes if available.
- Preferred scoring scale if provided.
Workflow
- Extract expected behaviors and forbidden behaviors.
- Convert each behavior into a measurable criterion.
- Tie each criterion to prompt evidence, policy evidence, or a clearly labeled assumption.
- Add representative test cases, including edge cases.
- Define pass/fail assertions and scoring guidance.
- Preserve uncertainty where behavior is underspecified.
Output
Produce Markdown with:
- Eval Goal
- Rubric Table
- Test Cases
- Assertions
- Failure Modes
- Scoring Notes
- Missing Requirements
Validation
- Criteria are observable in outputs.
- Assertions can be judged consistently.
- Safety and correctness are not traded away for style.
- Ambiguous prompt requirements become missing requirements.
- Test cases include at least one likely failure case.