jevaluate-evallisted
Install: claude install-skill tiffygk/jev-mode
# Jevaluate Eval
Tests whether graders apply the jevaluate rubric correctly, and proposes wording fixes. It never edits `rubric.md`, `read.md` or the library. If `$JEVALUATE_OVERLAY` is set, read that file first; its rules override the defaults here.
The scripts are in `jevaluate-eval/` (the quiz in `jevaluate-eval/quiz/`); every command is in `commands.md`. The runners refuse while `jevaluate/` or `jevaluate-harness/` has uncommitted changes, or `main` is ahead on them: commit or merge first.
## Four instruments, in order
Before each, tell the owner in one line which runs next and what it tests.
1. **Materials check: does what a grader reads say what the rules mean?**
- `lint_materials.py` must print "lint clean": allowed values, eval-case names, em-dashes, named files, a `jevaluate/enforcement.md` row for every rule, and no sentence over 35 words added since the newest freeze.
- A fresh reviewer, briefed as a grader, reads them for contradictions.
- `build_grader_view.py <out.html>` builds the step-by-step view: the rater's start files, what `step.py` serves at each phase, every stakes row, and the eval grader's prompt. The owner reviews it. Schedule that review after any planned task that moves instructions into code, never before.
2. **Quiz: does a grader understand the rules on invented projects?**
- Ask the owner how many scenarios they'll answer. Default 12: 8 tuning, 4 held out.
- A writer that never sees the rules writes them (a headless call with