Skip to content
Skills Library
Marketing & content · Review & audit

reader-sim

/reader-sim

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.

Licence
Apache-2.0
Last repository change
25.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

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.

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

How it works

  1. Method
Original SKILL.md headings · 47 lines, 400 words
SKILL.md preview
---
name: reader-sim
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.
---

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

Versions

The database has no other skills named reader-sim.

Identical content appears in 2 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version f2db2e756ac3 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100persona-read-loop
    Have three isolated LLM reader personas read a draft (article, README) in rounds, revise only how it is shown, and count what each revision added. Use when checking whether a draft gets across before the author reads it (ペルソナに読ませて).
  • 100reader-panel
    This skill should be used when the user asks for a "simulated beta read", "reader panel", "persona read", "first read before my beta readers", "how would a genre reader react", "would a reader keep going", "pre-beta read", "mock beta readers", or wants structured persona reads…
  • 90audience-adaptation
    Adapt what you write, how much, and how you frame it to the specific reader's knowledge, needs, and stakes. Use when the same content must reach different audiences, or when writing is missing its reader.
  • 100editorial-reader-reviewer
    Review an article for reader usefulness, clarity, structure, progression, examples, unanswered questions, skimmability, and reading flow. Use when an agent needs an independent audience-focused review before revision.
  • 100blog-review
    Review a technical blog draft and report what loses its reader, ordered by cost. Use when asked to review, critique, give feedback on, or tighten a draft blog post, article, newsletter issue, or engineering essay, or to 审稿 / 看看这篇. Do NOT use for READMEs, guides, comments, or…
  • 90improve-readability
    Use when editing prose for clarity, grammar, flow, and reader impact. Applies reader-first principles and a reference bank, including Claudisms, while preserving meaning and voice.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.