user-uatlisted
Install: claude install-skill aberson/skill-mesh
# User UAT
> **Judging doctrine:** the mechanical-gates-first, evidence-on-every-verdict, and low-confidence-escalates invariants behind this skill's partition live in [`_shared/judge-core.md`](../_shared/judge-core.md) — this skill instantiates them for the UAT-execution case.
Execute an **already-clear** UAT block so the operator doesn't have to be the mechanical
relay (run command → eyeball output → paste it back). The skill runs each step, captures
the real result, and **auto-judges only the deterministically-checkable steps**; everything
that needs judgment is escalated with the evidence attached.
It does **two things deliberately NOT**: it does not *refine* a fuzzy script (that is
`/review-uat`), and it does not *replace the operator* for checks that genuinely need a
human. The win is the mechanical tier — which is most of the volume.
## When to use / not
- **Use:** a concrete UAT exists — a `Type: operator` plan M-step, a build-phase "Manual UAT"
bundle, the "commands + what to look for" table from a handoff, or the operator pasting
"run these and tell me what happens." Steps have commands and observable expectations.
- **Don't use** to write or refine a UAT. If steps are ambiguous (verb with no object, "expect
X" with no observable, no pass criteria), **STOP and delegate to `/review-uat`** — do not
guess what a step means. A run built on a guessed expectation is worse than no run.
## Invocation
```text
/user-uat # use the UAT block