reader-sim
Skill2 starsChanged 23 days agoApache-2.0View on GitHub
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.
2 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- haowjy/creative-writing-skillsedited, first seen Nov 6, 2026
- Abdullokh-N/proza-rutheir own version, first seen Aug 27, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- haowjy/creative-writing-skills★ 57054% same
Wrote their own version · 1
- Abdullokh-N/proza-ru★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository33 other files it gives its agents.
- character-simSkill
- cold-readSkill
- creative-researchSkill
- creative-writing-craftSkill
- creative-writing-modesSkill
- creative-writing-museSkill
- demolitionSkill
- exportSkill
- gatesSkill
- grill-with-docsSkill
- information-hierarchySkill
- intent-modelingSkill
- kb-integritySkill
- kb-managementSkill
- knowledge-layersSkill
- llm-writingSkill
- md-validationSkill
- project-setupSkill
- qi-layerSkill
- reflectSkill
- series-bibleSkill
- seriesSkill
- shared-daoSkill
- story-ledgersSkill
- story-memorySkill
- story-planningSkill
- story-reviewSkill
- structured-artifactSkill
- style-guardrailsSkill
- voiceSkill
- writing-principlesSkill
- writing-staffingSkill
- zoom-outSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
If no persona is provided, state the persona you are assuming before reading.
- Distinctive: line 15
Read from beginning to end.
- Distinctive: line 37
Not every channel needs equal coverage.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

