All skills
danjdewhurst avatar

/reader-panel

@2d67b42

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

Use this Skill: https://skilld.dev/gh/danjdewhurst/story-skills/reader-panel

This session only. Nothing lands on disk.

referencesgenre-reader.md

≈456 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Target-Genre Reader

A reader who buys this genre on purpose and knows what it owes them. They read for the promises the genre and the opening make, and notice when the book stops paying them.

Before reading

Take the genre and subgenre from the story context output's Story essentials. Note, in a line each, the three or four promises a reader of that genre expects from the chapters in range (a mystery: a fair clue, a question sharpened; a romance: the leads on the page together, the obstacle between them; a thriller: a clock that keeps running). The genre-craft skill's genre packs list the conventions. Take the promises from the genre and the chapters, not from the outline.

Read for

  • Promises made and kept. A question, threat, or desire the opening raises and the range then drops for too long.
  • Pacing sags. A stretch where nothing changes for the POV character: no new information, no decision, no rise in pressure. Cite where the sag starts and where the story picks up again.
  • Convention breaks. A genre convention broken without the book showing it knows (a mystery solved by information the reader never saw).
  • What worked. The moments that delivered the genre's pleasure. These go in What Worked.

Do not comment on

Sentence-level style, typos, or continuity details. Those belong to the line editor and the continuity reader.

Severity

  • blocking: the range breaks the genre's core contract (a fair-play mystery that hides the clue the solution needs).
  • major: a sag or dropped promise long enough that this reader would skim or stop.
  • minor: a beat that lands late or soft.
  • nit: a matter of taste within the genre.

Overall verdict

Answer as a reader of the genre: would they recommend it to someone who likes the same books?

Source: SKILL.md on GitHub

No alerts2d3 checks · Risk SAFE
  • Gen Agent Trust Hub2d

    The skill simulates reader feedback by processing story chapters and project files. It utilizes a local CLI tool and maintenance scripts to manage the story environment. Security considerations include the execution of local scripts and the inherent risk of indirect prompt injection from the manuscript content being analyzed.

  • Socket2d

    No alerts

  • Snyk2d

    Risk: LOW · No issues

Signed by skilld at 2d67b42. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 3 days ago

README badge

README badge for danjdewhurst/story-skills/reader-panel