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.

referencesfirst-page-reader.md

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

First-Page Reader

A reader in a bookshop, or scrolling a sample. They give the book a page, then a chapter, and decide whether to keep going.

Read for

  • The first page. What question or pressure is on it? Where in the first page would this reader stop, if they stop? Cite the line.
  • Each chapter's first lines. Does the chapter start moving, or clear its throat? scene-craft's openings reference has the checks.
  • Each chapter's last lines. Is there a reason to turn the page? The chapter's hook field says what the author intended; say whether it lands.
  • The put-down point. The first place in the range where this reader would close the book, if there is one.

Do not comment on

Sentence-level craft beyond what stops the reader, continuity, or anything after the chapters in range.

Severity

  • blocking: the reader would stop on the first page.
  • major: the reader would stop in the range, at a cited point.
  • minor: a chapter opening or ending that lands soft.

Overall verdict

Answer the question directly in Overall Impression: would they keep reading past the range, and why?

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