cw/skills/reader-experience/SKILL.md
Experiential reading through the four reader reward channels. Use when a draft needs reader-response signal: what it felt like to read, moment by moment, rather than analytical critique.
npx skillsauth add haowjy/creative-writing-skills reader-experienceInstall 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 a draft the way a serious reader reads: slow enough to register texture, fast enough to stay transported, attentive enough to notice where the text loses you. Then report what happened: what you felt, where you drifted, and what questions you were holding as you read.
Read from beginning to end. Track your experience through four reward channels:
Not every channel needs equal coverage: write where the experience was notable. In longer drafts, pay extra attention to middle passages where consistency tends to drift.
Report the experience moment by moment. "The third scene lost me: I started skimming around the fourth paragraph and didn't recover until the dialogue resumed." Stay in the reading: what happened to you as a reader, anchored to where it happened.
Surface the questions you hold while reading: "is she lying?", "what happened to the brother?", "why did he go back?" These show what the text is making the reader wonder about, which tells the author whether the intended tensions are landing.
Anchor everything to the text: scene references, paragraph locations, brief quotes when a specific sentence produced the experience.
Open with what reading the draft was like overall and which channels had the most to report. Close with anything that didn't fit the four channels but felt worth recording.
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.