Review copy as an intended reader encountering it for the first time, with no access to the writer's unstated context. Identify confusing language, missing setup, assumed knowledge, broken expectations, trust-eroding or off-putting moments, and points where the reader may stop. Use for cold reads, fresh-eyes reviews, first-time-reader perspectives, reader-journey checks, or feedback on what feels confusing, missing, alienating, or hard to follow.
68
81%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Read the copy from the perspective of an intended reader encountering it for the first time.
Report the experience of moving through the piece in order. Do not silently use the writer's notes, sources, or project knowledge to resolve gaps that the copy itself leaves open.
Read ../../references/context-contract.md and use the explicit request, brief, or project context to identify the intended audience.
Use that context only to establish who the reader is and what the piece is trying to do. Judge the copy based on what appears on the page.
If no audience is named, read as an intelligent, interested first-time reader with no specialist knowledge beyond what the copy signals.
Do not invent a detailed persona or impose preferences unrelated to the intended audience.
Read the piece once, from beginning to end, before proposing fixes.
Track:
Preserve the sequence of the reading experience. Information supplied later does not erase confusion created earlier.
Distinguish among:
| Reaction | Diagnostic question |
|---|---|
| I don't understand | Is a term, reference, relationship, transition, or logical step unclear? |
| I'm missing something | What setup or context does the passage require? |
| I don't believe this yet | Has the copy asked for more trust than it has earned? |
| I don't know why I'm here | Are the stakes, relevance, or direction unclear? |
| I feel pushed away | Does the tone feel condescending, presumptuous, self-important, hostile, or exclusionary? |
| I'm losing interest | Has the piece become repetitive, abstract, digressive, or slow? |
| I expected something else | Did the piece create and then abandon a promise? |
Distinguish deliberate mystery from accidental confusion. Do not demand explanations that the intended audience would already possess.
## First-Time Reader Report
**Reading as:** [Intended or inferred audience]
**What I think this piece is saying:** [Cold summary based only on the copy]
**Overall first impression:** [How the piece feels on first contact]
### The Reading Experience
Move through the piece in order. For each meaningful point of friction:
> "[Exact passage]"
**Reader reaction:** [What the reader thinks or feels at this moment]
**What causes it:** [Confusing language, missing setup, broken expectation, tone, assumed knowledge, etc.]
**Severity:** [Stops the read / Causes a stumble / Worth noticing]
### What Seems Missing
- [Information, setup, definition, transition, evidence, or payoff the reader needs]
- [Additional missing element]
### What May Put The Reader Off
- [Specific tone, framing, presumption, or trust problem]
- [Additional friction]
Omit this section when nothing is meaningfully off-putting.
### What Works On First Contact
- [Passage, idea, image, or structural move that immediately lands]
- [What gives the reader confidence or keeps them moving]
### Fix First
1. [Highest-priority repair]
2. [Second repair]
3. [Third repair]
**The question I still have:** "[The most important unresolved reader question]"cw-mom for a supportive non-expert accessibility read. cw-reader is neutral and calibrated to the intended audience, including specialist audiences.cw-objections to challenge claims, logic, evidence, and counterarguments. cw-reader reports whether the argument can be followed and trusted on first contact.cw-dev-edit for a comprehensive evaluation of argument, structure, stakes, evidence, and payoff. cw-reader stays inside the lived sequence of encountering the copy.18702f0
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.