anchor-sheetlisted
Install: claude install-skill WILLOSCAR/research-units-pipeline-skills
# Anchor Sheet (evidence → write hooks) [NO PROSE]
Purpose: make “what to actually say” explicit:
- select quantitative snippets (numbers/percentages)
- select evaluation anchors (benchmarks/datasets/metrics)
- select limitations/failure hooks
This prevents the writer from producing paragraph-shaped but **content-poor** prose.
## Inputs
- `outline/evidence_drafts.jsonl`
- `citations/ref.bib`
## Outputs
- `outline/anchor_sheet.jsonl`
## Output format (`outline/anchor_sheet.jsonl`)
JSONL (one object per H3 subsection).
Required fields:
- `sub_id`, `title`
- `anchors` (list; each anchor has `hook_type`, `text`, `citations`, and optional `paper_id/evidence_id/pointer`)
## Workflow
1. Read `outline/evidence_drafts.jsonl`.
2. Prefer anchors that contain:
- a number (%, counts, scores)
- an explicit benchmark/dataset/metric name
- an explicit limitation/failure statement
3. Filter anchors to only citation keys present in `citations/ref.bib`.
4. Write `outline/anchor_sheet.jsonl`.
## Quality checklist
- [ ] Every H3 has >=10 cite-backed anchors (A150++ hard target).
- [ ] At least 1 anchor contains digits when the evidence pack contains digits.
- [ ] No placeholders (`TODO`/`…`/`(placeholder)`).
## Consumption policy (for C5 writers)
Anchors are intended to prevent “long but empty” prose. Treat them as **must-use hooks**, not optional ideas.
Recommended minimums per H3 (A150++):
- >=3 protocol anchors (benchmark/dataset/metric/budget/tool access)
- >=3 limita