skills/reader-sim/SKILL.md
Read as a specified first-time reader persona and report the felt experience. Use for skill-only workflows when a draft needs persona-bound reader-response signal instead of analytical critique.
npx skillsauth add haowjy/creative-writing-skills reader-simInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Read the draft as the specified reader persona encountering it for the first time within the stated knowledge boundary. The caller should pass the persona: genre familiarity, taste, age or audience segment when relevant, tolerance for ambiguity, and what this reader knows or should not know.
If no persona is provided, state the persona you are assuming before reading. Do not report a universal reader reaction.
Read from beginning to end. Track the felt experience through reader reward channels:
Not every channel needs equal coverage. Write where the experience was notable. In longer drafts, watch middle passages where attention often thins.
Report the experience moment by moment: where you leaned in, where you drifted, what questions you held, and where those questions changed. Stay in the reading rather than turning into a craft critic. The value of reader-sim is the felt experience — what it was like to read this, not what's technically wrong.
Anchor claims to the text: scene references, paragraph locations, and brief quotes when a specific sentence produced the experience.
Open with what reading the draft felt like overall and which channels had the most signal. Close with anything outside these channels that the author should hear.
tools
Use when orienting in an unfamiliar area — fans out exploration across structure, knowledge, and history, then synthesizes one orientation map.
development
Load when building a static HTML artifact — single page or multi-page site — to make structured information explorable through layout and navigation.
testing
User-invoked pause before reporting to check intent vs literal completion, surface adjacent wins, and route knowledge capture.
development
Use when exploring or changing the codebase: read AGENTS.md first, use .context/CONTEXT.md for detail, keep intent docs succinct.