reader-sim — Claude Code skill: reader feedback and setup
This skill reads a draft as a specified first-time reader and reports how the experience changes from scene to scene. Use it when you want a persona-based response rather than a craft critique.
npx skills add haowjy/creative-writing-skills --skill reader-sim -a claude-codeWhat reader-sim does
Give it a reader persona before the draft: genre familiarity, tastes, relevant age or audience segment, tolerance for ambiguity, and what the reader knows. If you leave out the persona, the skill states the one it assumes. It does not present that response as universal.
The skill follows the text from beginning to end, noting moments of immersion, shifts in attention, questions the reader carries, and changes in interest. It tracks reactions to the story world, prose, characters, curiosity, and reading flow, then anchors them to scenes or brief quotes. The report opens with the overall reading experience and closes with anything the author should hear beyond those channels. It stays with felt response, so it does not replace a technical critique of the draft.
What it helps with
- Get a draft response from a defined first-time reader
- Find where a story holds attention or loses it
- Track the questions a reader carries through a draft
- Check whether a character’s motives make sense to a persona
Example prompts for the agent
- Read this draft as a first-time reader who knows little about the genre, and tell me where you get drawn in.
- Respond as a reader who dislikes ambiguity; stay within what the text tells you.
- Follow your questions scene by scene and note where you stop caring about what happens next.
How to install reader-sim
1Skills CLI (Vercel)
npx skills add haowjy/creative-writing-skills --skill reader-sim -a claude-code2Manually: put the files in place
~/.claude/skills/reader-sim/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/reader-sim/
1Skills CLI (Vercel)
npx skills add haowjy/creative-writing-skills --skill reader-sim -a codex2Manually: put the files in place
.agents/skills/reader-sim/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add haowjy/creative-writing-skills --skill reader-sim -a cursor2Manually: put the files in place
.cursor/skills/reader-sim/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install haowjy/creative-writing-skills reader-sim2Manually: put the files in place
.github/skills/reader-sim/SKILL.md1Skills CLI (Vercel)
npx skills add haowjy/creative-writing-skills --skill reader-sim -a gemini-cli2Platform CLI
gemini skills install https://github.com/haowjy/creative-writing-skills --path skills/reader-simManually: put the files in place
.devin/skills/reader-sim/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add haowjy/creative-writing-skills --skill reader-sim -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about reader-sim
How do I install reader-sim in Claude Code?
Run npx skills add haowjy/creative-writing-skills --skill reader-sim -a claude-code. The skill file is at ~/.claude/skills/reader-sim/SKILL.md.
What does reader-sim do?
It reads a draft as a specified reader encountering it for the first time, then reports the felt experience with references to scenes and brief quotes.
What should I include in a reader persona?
Describe genre familiarity, taste, tolerance for ambiguity, and what the reader knows or should not know. Without a persona, the skill states the one it assumes.
Source text
SKILL.md · Apache-2.0
--- name: reader-sim type: mode-shift description: > 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. model-invocable: true --- # Reader Simulation 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. ## Method Read from beginning to end. Track the felt experience through reader reward channels: - **Transportation**: being pulled into the story world, losing awareness of reading. Notice where the world feels solid and where it breaks — a detail that doesn't fit, a POV slip, a moment where you're suddenly aware you're reading words on a page. - **Aesthetic**: pleasure from language, rhythm, imagery, craft. Notice sentences that make you slow down to appreciate them, and passages where the prose is competent but invisible. - **Social simulation**: modeling characters as minds. Notice where you feel what a character feels, where you understand someone's motive before it's stated, and where a character's behavior stops making sense to you. - **Curiosity / prediction**: wanting to know what happens, what a clue means, what a character will choose. Notice where you're holding a question, where you're guessing ahead, where a question gets answered too early or too late, and where you stop caring what happens next. - **Flow**: the reading feeling absorbing and easy to stay with. Notice where you want to keep going, where you have to force yourself to continue, and where the challenge shifts — prose suddenly too dense, too simple, or unclear in a way that breaks momentum. 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.
© haowjy · Apache-2.0 · haowjy/creative-writing-skills