tap-to-judgelisted
Install: claude install-skill tsetse012/tap-to-judge
# tap-to-judge
The person reviewing is a **calibrator, not an inspector**. Their time buys you a rule change, not 40 individual corrections. So the review has to be fast, has to show its evidence, and has to return machine-readable data.
**Never ask for 20+ verdicts in chat.** Build one board.
## 1. When
- More than ~10 human verdicts needed (fewer than that, just ask in chat)
- Golden-set curation · labelling · false-positive sampling · candidate acceptance · draft review
- Any time the verdicts will be **aggregated to decide a rule**
## 2. How
```bash
# 1. Write data.json — see the contract below.
# Ship the RAW SOURCE for each item, never only your own summary (LESSONS #1).
python3 ~/.claude/skills/tap-to-judge/build.py build data.json board.html
# 2. Publish as an Artifact with capabilities: {"artifact": {}} <- required for Save
# 3. The user judges and saves. A republish notification arrives.
# 4. Read it back: Artifact action:"read"
python3 ~/.claude/skills/tap-to-judge/build.py collect <path the read saved>
```
`collect` returns `verdicts` (per item) · `tally` (count per verdict) · `drop_reasons` (rejection
types) · `added` (what the user said was missing) · `judged`/`total`.
**Unjudged items are not counted.** Blank is not a "no".
## 3. Data contract
```json
{
"title": "What is being judged",
"subtitle": "optional line under the title",
"intro": "2-3 lines: what to look at and what to pick",
"synthetic": false,
"allow_add": true,
"source_l