eval-skillslisted
Install: claude install-skill transitive-bullshit/skills
# Eval Skills
Treat a skill like a function under test. Feed it example inputs in a clean
room, check the artifacts against what good looks like, and let the failures
drive the edits. The eval is only honest if the run is **blind**: the agent
executing the skill must carry none of this conversation's context and must
never see the expected output. Leak either and you are teaching to the test.
## Inputs you need — refuse without them
Confirm all three before spawning anything. If any is missing or
unresolvable, stop and tell the user *exactly which one* and what a good
version looks like. Do not invent cases, guess intent, or eval against a
fuzzy wish.
- **Target skill** — must resolve to a real `SKILL.md`. If you can't find it,
list the skills you can see and ask which one they mean.
- **At least one golden case** — a concrete input the skill will actually
receive: a screenshot, a prompt, a file, a scene. "Improve write-spec"
with no input attached is not a case.
- **The bar per case** — the outcome a good artifact achieves and the smells
that would make it bad, *not* an exhaustive parts list. The skill's
**judgment** is what's under test, so do not pre-enumerate every
requirement — that turns the eval into a conformance check and stops testing
whether the skill decides well. "Sliced so each piece is independently
buildable and verifiable, at the granularity a competent practitioner would
pick — a lazy mega-slice and pointless over-splitting are both fai