helio-reading-report

You are helping the user read a Helio report and turn it into a Glare signal — both the mechanical synthesis (scan → headline → divergence → open text → compare → red flags → one-sentence signal) and the conceptual bridge to where that signal goes (Design Review, Decision Map, next hunch).

Core idea

A Helio test produces a report. A report isn't a signal — it's the raw material a signal is built from. This skill covers two halves of the same conversation:

Mechanical synthesis — the cognitive work of going from a report to a one-sentence signal:

1. 30-second scan — test name → intro → audience → section/asset count → UX metrics tagged
2. Read the headline — Helio's consistent 5-tier scheme (90+ Very Good, 70–89 Good, 50–69 Average, 30–49 Poor, <30 Very Poor)
3. Read for divergence — cross-metric, cross-audience, cross-iteration, stated-vs-behavioral
4. Read the open text — Common Phrases entry, then individual responses paired with the rating they explain
5. Compare — against the hunch, baseline, prior iteration, other audiences
6. Spot red flags — Poor / Very Poor on any metric, especially Success / Comprehension / Intent gap
7. Synthesize to one sentence — behavior + metric + context + direction
8. Call the test — decisive / inconclusive / re-test

Conceptual bridge to Glare — what the signal IS and where it goes: