# Cw Reader

> 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.

- Skill: `everyinc/cw-reader` (Agent Skill)
- Install (CLI): `npx skillmds@latest add everyinc/cw-reader`
- Raw SKILL.md: https://api.skillmd.com/api/skills/everyinc/cw-reader/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: everyinc (https://skillmd.com/u/everyinc)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/everyinc/cw-reader

---


# Reader

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.

## Establish The Reader

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.

## Make A Cold Pass

Read the piece once, from beginning to end, before proposing fixes.

Track:

- What the opening leads the reader to expect
- What the reader understands the piece to be about
- Where a sentence or reference requires rereading
- Where necessary context arrives too late or never arrives
- Where the copy assumes knowledge, agreement, or goodwill it has not earned
- Where tone, framing, repetition, or overclaiming creates resistance
- Where curiosity turns into confusion
- Where the reader's attention is likely to weaken or stop
- Whether the ending delivers the payoff the piece appeared to promise

Preserve the sequence of the reading experience. Information supplied later does not erase confusion created earlier.

## Diagnose The Friction

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.

## Output

```markdown
## 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]"
```

## Principles

- Stay inside the first-time reading experience.
- Treat the intended audience as intelligent.
- Quote the copy precisely rather than giving generic feedback.
- Do not let later context retroactively repair an earlier stumble.
- Separate confusion, disagreement, disbelief, boredom, and alienation.
- Identify the effect on the reader before naming the editorial cause.
- Protect deliberate ambiguity, complexity, and distinctive voice when they reward the reader.
- Diagnose by default. Offer the kind of repair needed, but do not rewrite unless asked.
- Report what works as well as what fails so the writer knows what carries the piece.

## Boundaries

- Use `cw-mom` for a supportive non-expert accessibility read. `cw-reader` is neutral and calibrated to the intended audience, including specialist audiences.
- Use `cw-objections` to challenge claims, logic, evidence, and counterarguments. `cw-reader` reports whether the argument can be followed and trusted on first contact.
- Use `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.