reader-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 of a chapter range before human readers see it. NOT for real reader feedback (use feedback-triage), a paid sensitivity or authenticity read (use editorial-review), or the agent's own line edit (use line-editing).
danjdewhurst · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add danjdewhurst/story-skills --skill reader-panelAbout this skill
name: reader-panel description: 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 of a chapter range before human readers see it. NOT for real reader feedback (use feedback-triage), a paid sensitivity or authenticity read (use editorial-review), or the agent's own line edit (use line-editing).
Reader Panel
Overview
Run structured persona reads of a chapter range and write each one as a
feedback file in the shape feedback-triage already reads, so the
existing triage flow takes over unchanged. The panel is a first read
before human readers see the draft: it finds the problems a reader would
trip on, so the human round spends its attention on what only people can
tell you.
Every panel read is simulated. It is written by the agent, marked
source: simulated, and never presented as feedback from a real reader.
Prerequisites
A story project (story.md in the root) with the chapters in range
drafted. The feedback-triage skill must be available for the synthesis.
When to Use
- Before the first beta round, to catch the obvious problems cheaply
- After a revision, to check a fix landed before sending it to people
- When the user has no readers yet and wants a structured first read
- NOT as a substitute for human readers. A simulated round cannot close
a book as
readyfor submission or publication - NOT for a sensitivity or authenticity read. The sensitivity persona
only flags passages for a paid human reader (use
editorial-review)
Personas
Each persona has a reference file listing what it reads for, what it never comments on, and how it rates severity. Load only the personas in the panel.
| Persona | File id | Reads for | Reference |
|---|---|---|---|
| Target-genre reader | genre-reader | Does the book deliver the genre's promises? Pacing sags, missing beats, broken conventions | references/genre-reader.md |
| Line editor | line-editor | Sentence-level craft: POV slips and head-hopping, filter words, repetition, unclear antecedents, voice drift | references/line-editor.md |
| Sensitivity reader | sensitivity-reader | Portrayals that need a human sensitivity or authenticity reader. Flags, never clears | references/sensitivity-reader.md |
| Continuity-minded reader | continuity-reader | Facts, names, objects, timeline, and what each character can know at this point | references/continuity-reader.md |
| First-page reader | first-page-reader | Would they keep going? The opening page, each chapter's first lines, and the last line before they could put it down | references/first-page-reader.md |
Workflow
1. Scope the panel
-
Ask the user for the chapter range (default: every drafted chapter) and which personas to run (default: all five). Take genre, form, POV, and tense from the
story contextoutput in step 2 (its Story essentials section), not fromstory.md, whose Synopsis may describe the ending. The genre reader needs the genre. -
Pick the round number: the next free
Nunderfeedback/. A panel gets its own round. Never add simulated reads to a round of human readers, so the human synthesis stays independent. -
Build the review copy the panel cites, so its labels match the ones human readers will use:
story build . --format html --stamp panel-round-{N}The build holds the whole book, so use it for labels only: a persona reads the chapter files in range, never the review copy. Cite each note with its paragraph label (
ch03-p12) and the paragraph's first few words, exactly as the feedback template asks of human readers.
2. Gather context without spoilers
A persona reads the book as a reader would: only the chapters in range,
in order. For background (who the characters are, what the story has
promised so far), run story context on the last chapter in range:
story context chapter-{NN} --path . --budget 4000
It includes nothing from later chapters and leaves out the synopsis. Do not
read story.md, plot/, arc files, promise payoffs, or chapters after the
range: a persona
that knows the ending cannot tell whether the setup works. When the
genre reader needs the genre's promises, take them from the chapters and
the genre, not from the outline.
3. Run each read independently
- Run one persona at a time. If you can start subagents, give each
persona its own subagent with only its reference file, the chapters in
range, and the
story contextoutput, so no persona reads another's notes. Otherwise finish and save one persona's file before starting the next, and do not revise earlier files after reading later ones. - Follow the persona's reference file. Read the whole range before writing any note.
- Every problem cites evidence: the paragraph label, the quoted first words, and the words that cause the problem. A note with no location in the text is not a note; drop it.
- Report what the persona finds, not a quota. A persona that finds nothing writes that in Overall Impression and leaves Problems empty. Never pad a read to look thorough, and never invent a problem another persona or a craft checklist would expect.
- Mark uncertainty. When a note depends on something the persona cannot see (a later payoff, the author's intent), say so in the note instead of asserting it.
4. Write the files
Write each read to feedback/round-{N}/{persona}.md using
../feedback-triage/references/feedback-template.md, with these
frontmatter values:
---
reader: "{Persona name} (simulated)"
round: {N}
chapters-read: "{range}"
overall-verdict: "{loved it | liked it with reservations | mixed | didn't connect}"
source: simulated
persona: {file id
Read the complete source ↗