A skill your agent uses when you want beta reader feedback on your draft from three sharply different test readers, one who reads for pace, one who reads for depth, and one who hunts for plot holes…

MITAuto-check passedWriting & Content

Install Beta Reader

skills CLI
$ npx skills add felipelobomotta-blip/book-genesis-studio --skill beta-reader -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install felipelobomotta-blip/book-genesis-studio beta-reader --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/felipelobomotta-blip/book-genesis-studio.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/beta-reader .claude/skills/beta-reader && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
beta-reader
GitHub stars
139
Token cost
~2.4k tokens
SKILL.md length
1,336 words
Files
4 (incl. references)
Skills in repo
4
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when you want beta reader feedback on your draft from three sharply different test readers, one who reads for pace, one who reads for depth, and one who hunts for plot holes…

  • Works in 6 steps: Collect the text. A chapter, a part, or… → Infer what you can. Genre, audience, and… → Check scope. The readers are built for… → …
  • You want beta reader feedback on your draft from three sharply different test readers
  • SKILL.md covers The readers, What the readers may see, Process and Reading rules for all three…, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Beta Reader is an agent skill from felipelobomotta-blip/book-genesis-studio. Use when you want beta reader feedback on your draft from three sharply different test readers, one who reads for pace, one who reads for depth, and one who hunts for plot holes and weak logic. Each reads your pages in order and reports where they would stop reading, what confused them, and what they loved, quoting your own lines. You also get a map of where attention drops and a short list of what to fix first, separating the problems all three readers agree on from matters of taste. Works on a chapter, a part…

Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/critic.md`, `references/page-turner.md` and `references/skeptic.md`).

It sits in Writing & Content, covering Creative writing and fiction. The repository describes itself as: Open-source writing skills for Claude Code, Codex, OpenCode, Antigravity, Gemini, OpenClaw, and Hermes. Your creativity. Your agent. Your book. The licence is MIT.

When your agent uses it

  • You want beta reader feedback on your draft from three sharply different test readers
  • One who reads for pace
  • One who reads for depth
  • One who hunts for plot holes and weak logic

Example prompts

  • “/beta-reader”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Collect the text. A chapter, a part, or the whole manuscript: pasted, one file, or a folder of chapter files read in order. Note what was…
  2. Infer what you can. Genre, audience, and language come from the text when the author did not say. State your guess at the top of the…
  3. Check scope. The readers are built for prose books: novels, novellas, story collections, memoir, and narrative or practical nonfiction…
  4. Set the language. Write the whole report in the manuscript's language unless the author asks for another one. A Portuguese draft gets a…
  5. Run the readers apart. If your host can run subagents, give each reader its own subagent with only: the text (plus title, genre, and…
  6. Write the synthesis (below), then the honesty lines.

What it can do on your machine

Read from SKILL.md and the folder at commit 46a744f. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Beta Reader loads about 2.4k tokens when it runs, and up to ~5.5k if it reads all its reference files. Until then it costs about 190 tokens; SKILL.md has 1,336 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~190
When it runs · the whole SKILL.md, loaded when a task matches
~2.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from felipelobomotta-blip/book-genesis-studio at commit 46a744f, republished under its MIT licence (© felipelobomotta-blip). 1,336 words, ~2,436 tokens.

Download SKILL.mdSave it as .claude/skills/beta-reader/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
beta-reader
description
Use when you want beta reader feedback on your draft from three sharply different test readers, one who reads for pace, one who reads for depth, and one who hunts for plot holes and weak logic. Each reads your pages in order and reports where they would stop reading, what confused them, and what they loved, quoting your own lines. You also get a map of where attention drops and a short list of what to fix first, separating the problems all three readers agree on from matters of taste. Works on a chapter, a part, or a whole novel, memoir, or nonfiction book, in any language, and the report comes back in the language of your book. The readers are simulated, not real people, so use them to find what to fix before real readers see the book.

Beta Reader

Three simulated readers with different tastes, habits, and tolerances read the draft in order and report honestly. The goal is diagnosis, not praise: where each reader would stop, what confuses them, what delights them, and what is missing.

Why three and not ten: one model playing many readers produces many versions of the same bias. Three readers with deep, conflicting instructions give more signal and less noise. When all three flag the same problem from their own angles, it is real. When only one does, it may be taste.

The readers

ReaderReads forQuits whenBrief
The Page-Turnerpace, feeling, momentumpatience runs outreferences/page-turner.md
The Criticdepth, originality, precisionthey stop trusting the authorreferences/critic.md
The Skepticlogic, consistency, credibilitya hole breaks beliefreferences/skeptic.md

Each brief is long on purpose. Load a reader's brief only for that reader's pass.

What the readers may see

Readers know only what a real reader knows before opening the book: the title, the genre, and the back-cover copy if the author has one. They never see the outline, synopsis, author notes, research, or earlier feedback.

If the author has an outline, a synopsis, or goals for the book, read them yourself, but keep them away from the readers. They feed only the final "What you meant vs what readers felt" section.

If you are given a middle chapter on its own, the readers may read a short summary of what came before (and nothing after), the way a returning reader remembers the story. Say so in the report.

Process

  1. Collect the text. A chapter, a part, or the whole manuscript: pasted, one file, or a folder of chapter files read in order. Note what was read, for example "chapters 1-8 of 24" or "full manuscript".
  2. Infer what you can. Genre, audience, and language come from the text when the author did not say. State your guess at the top of the report instead of asking.
  3. Check scope. The readers are built for prose books: novels, novellas, story collections, memoir, and narrative or practical nonfiction. For poetry, picture books, or scripts, say so and offer a lighter read.
  4. Set the language. Write the whole report in the manuscript's language unless the author asks for another one. A Portuguese draft gets a Portuguese report, read by readers of that market with that market's references. Translate the reader names naturally. Quote passages exactly as written, never translated.
  5. Run the readers apart. If your host can run subagents, give each reader its own subagent with only: the text (plus title, genre, and back-cover copy if any), that reader's brief, the reading rules, and the report format below. If it cannot, run the readers one at a time in this conversation, finish each report before starting the next, and never revise an earlier report after writing a later one. Record which way you ran them.
  6. Write the synthesis (below), then the honesty lines.

Reading rules for all three readers

  • Read in order. No skipping ahead, no reading the ending first.
  • For a long manuscript, read in consecutive parts and keep a running log for each reader, so the stop points are real.
  • Quote exactly. Locate every point by chapter and page, or by a short quote the author can search for.
  • When a reader quits, record the quit point, then keep reading as a favor to the author. Mark everything after it "read past my quit point", and say whether anything later would have won them back.
  • Stay in character. Each reader reports only from their own seat. Fairness happens in the synthesis, not in the reader reports.

Report order

  1. Header: what was read, the genre and audience (stated by the author or guessed by you), and the language.
  2. The three reader reports, in this order: the Page-Turner, the Critic, the Skeptic.
  3. The synthesis.
  4. The honesty lines.

Report format for each reader

markdown
### [Reader name]
**Verdict:** Finished it / Quit at [location] / Finished out of duty
**Where I'd stop reading:** [location] "[quote]" [what went through my head]. If nowhere: "No reason to stop."
**Close calls:** [where I nearly quit, and what pulled me back]
**What confused me:** [location, what, why] or "Nothing."
**What delighted me:** [location] "[quote]" [why]
**Top 3 problems:** [each with a quote and a location]
**What's missing:** [what I wanted and never got]
**The morning after:** [the one image or line still in my head tomorrow] or "Nothing stuck."
**Engagement:** [X]/10, [one-line reason]
**Would I recommend it?** [yes or no, to whom, and in what words]
[The reader's own section, from their brief]

Verdicts, the same for all readers:

  • Finished it: kept reading because they wanted to.
  • Quit at [location]: would have stopped there for good; everything after it was read only as a favor to the author.
  • Finished out of duty: never hit a stopping point, but kept going without wanting to.

Engagement anchors, the same for all readers:

  • 3: quit early and would not come back
  • 5: would finish it only if stuck on a long flight
  • 7: finished it and was glad to
  • 9: would press it on friends
  • 10: among the best books I have read in this genre (rare)

Score like a stranger who paid for the book, not like the author's friend. Any score of 8 or more needs a quoted reason.

Synthesis: where the readers agree

Show full SKILL.md (548 more words)Show less
Agreement table
IssuePage-TurnerCriticSkepticCall

One row per issue or standout passage. In each reader's cell, write what that reader said in a few words, or leave it empty. Decide the call with these rules:

SituationCall
All three flag the same problemCritical: fix first
Two of three flag itReal problem: very likely worth fixing
Only one flags itMay be taste: look closely before acting
All three praise the same passageConfirmed strength: protect it in revision
The Skeptic praises itExceptional moment: probably a selling point
Only the Page-Turner quits, and inside the first chapterImportant anyway: an opening that loses a casual reader loses browsers too
Nothing stuck for any reader the morning afterImportant: the book has no moment people will remember
Convergence check

Agreement counts only when readers reach it from their own seats: the Page-Turner is bored in chapter 5, the Critic finds it cliched, the Skeptic does not believe it. That is three signals. If two reports flag the same passage for the same reason in similar words, count it once and write "readers converged here".

Attention map (more than one chapter)
ChapterPage-TurnerCriticSkeptic
1inindrifting

Map each reader's own log onto three words only: in, drifting, out. Two or more readers drifting or out in the same stretch marks a danger zone. Name it.

Fix first (at most five)

Order: logic and character problems first, then structure and pace, then line-level prose. Polishing a passage that will be cut is wasted work. Each fix names the location, the problem, and a concrete direction ("cut the town history in chapter 4 to one paragraph and move it after the body is found"), never just "tighten this".

Protect

The passages the revision must not touch, and why.

What you meant vs what readers felt

Only if the author shared goals, an outline, or a synopsis. One line per gap, for example: "You meant chapter 9 to devastate; the Page-Turner skimmed it and the Skeptic did not believe it."

Honesty lines (always the last lines of the report)
  • How the readers ran: "separate subagents, each seeing only the text" or "one after another in this conversation (less independent)".
  • Simulated readers: "These are AI-simulated readers, not real people. Use this report to decide what to fix and what to test with real readers; it does not replace them."
  • Self-review warning, only if you, in this conversation, wrote or rewrote any of the text: "Models tend to go easy on prose they helped write. Weigh the praise accordingly."

Saving the report

If you can write files, save the report beside the manuscript as beta-reader-report-YYYY-MM-DD.md, and never overwrite an earlier one. Otherwise, reply in the conversation.

If an earlier report exists, the readers still read blind; you compare afterwards: what got fixed, what is still there, and what is new, including problems the revision itself created.

When to use it

  • After each part of a draft. Don't wait for the whole book.
  • Before sending the manuscript to agents, editors, or real beta readers.
  • After a big revision, to check that the fix did not break something else.
  • When you are unsure whether a passage works.

This skill stands alone. The full idea-to-book workflow is the Book Genesis skill.

© felipelobomotta-blip, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in skills/beta-reader of felipelobomotta-blip/book-genesis-studio.

  • SKILL.md
  • references/critic.md
  • references/page-turner.md
  • references/skeptic.md

Open the folder on GitHubat commit 46a744f

Compare with similar skills

Beta Reader next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Beta Reader compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Beta Reader this skillfelipelobomotta-blip/book-genesis-studio139—~2.4kAutomated safety check: PassMIT
Story Multi-Perspective Reviewzenstory-ai/oh-story-claudecode7.4k3 repos~3kAutomated safety check: PassMIT
Story Toolbox Routerzenstory-ai/oh-story-claudecode7.4k1 repos~1.7kAutomated safety check: PassMIT
Short Web Fiction Trend Scanzenstory-ai/oh-story-claudecode7.4k3 repos~1.2kAutomated safety check: PassMIT
InkOS Creative HarnessNarcooo/inkos10k1 repos~1.1kAutomated safety check: PassAGPL-3.0
Novel Arteternityspring/shuohao-skills4.2k—~1.1kAutomated safety check: NotesApache-2.0

Similar skills

  • Story Multi-Perspective Review

    zenstory-ai/oh-story-claudecode

    Reviews Chinese web-novel text with several reviewer agents in parallel, falling back to a single-agent pass, and reports structure, character, prose and setting problems with fixes.

    7.4k GitHub starsUsed in 3 repos~3k tokens
    Writing & ContentAuto-check passed
  • Story Toolbox Router

    zenstory-ai/oh-story-claudecode

    Routes a Chinese web-novel writing request to the matching tool in a 13-skill toolbox, covers author habit memory, and can launch a local dashboard for browsing a project.

    7.4k GitHub starsUsed in 1 repo~1.7k tokens
    Writing & ContentAuto-check passed
  • Short Web Fiction Trend Scan

    zenstory-ai/oh-story-claudecode

    Scans popular short web-fiction rankings on Chinese platforms such as Dianzhong and Heiyan to surface trending emotional hooks, themes and topic candidates with an expiry warning.

    7.4k GitHub starsUsed in 3 repos~1.2k tokens
    Writing & ContentAuto-check passed
  • Drives long-form fiction, scripts, storyboards, interactive films and long-document translation through InkOS, with every change made by a typed action.

    10k GitHub starsUsed in 1 repo~1.1k tokens
    Writing & ContentAuto-check passed
  • Novel Art

    eternityspring/shuohao-skills

    给 AI 短剧出美术设定集(场景 + 叙事道具):场景的设计意图、一致性锚点、光照时段变体、 空景提示词;道具的戏剧功能、状态变体、尺度参照、白底无手提示词。

    4.2k GitHub stars~1.1k tokensUpdated 11 days ago
    Writing & ContentAuto-check: notes
  • Web Novel AI-Trace Remover

    zenstory-ai/oh-story-claudecode

    Rewrites AI-sounding Chinese web novel text so it reads naturally, changing as little as possible and keeping plot, names and numbers intact.

    7.4k GitHub starsUsed in 2 repos~2.6k tokens
    Writing & ContentAuto-check passed

More from felipelobomotta-blip/book-genesis-studio

  • Book Genesis

    felipelobomotta-blip/book-genesis-studio

    A skill your agent uses when someone wants to write a complete book from an idea, even a one-line one, or to continue, audit, revise or package a book in progress.

    139 GitHub stars~1.2k tokensUpdated 15 days ago
    Auto-check passed
  • Editorial Package

    felipelobomotta-blip/book-genesis-studio

    A skill your agent uses when your manuscript is finished and you need the writing that sells it.

    139 GitHub stars~3.7k tokensUpdated 15 days ago
    Auto-check passed
  • Literary Agent Panel

    felipelobomotta-blip/book-genesis-studio

    A skill your agent uses when you want to know how a literary agent, an acquiring editor, a bookseller, and a reader from your target audience might react to your book before you submit it.

    139 GitHub stars~1.9k tokensUpdated 15 days ago
    Auto-check passed

Questions about Beta Reader

What does Beta Reader do?

A skill your agent uses when you want beta reader feedback on your draft from three sharply different test readers, one who reads for pace, one who reads for depth, and one who hunts for plot holes…. Beta Reader is an agent skill from felipelobomotta-blip/book-genesis-studio. Use when you want beta reader feedback on your draft from three sharply different test readers, one who reads for pace, one who reads for depth, and one who hunts for plot holes and weak logic.

When should I use Beta Reader?

Beta Reader fits situations like: you want beta reader feedback on your draft from three sharply different test readers; one who reads for pace; one who reads for depth; one who hunts for plot holes and weak logic.

How do I install Beta Reader in Claude Code?

Run `npx skills add felipelobomotta-blip/book-genesis-studio --skill beta-reader -a claude-code`. Or copy the skill folder (skills/beta-reader in felipelobomotta-blip/book-genesis-studio) into .claude/skills/beta-reader in your project. Claude Code loads it when a task matches its description.

How do I install Beta Reader in Codex?

Run `npx skills add felipelobomotta-blip/book-genesis-studio --skill beta-reader -a codex`. Or copy the skill folder (skills/beta-reader in felipelobomotta-blip/book-genesis-studio) into .agents/skills/beta-reader in your project. Codex loads it when a task matches its description.

Can I use Beta Reader in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add felipelobomotta-blip/book-genesis-studio --skill beta-reader -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/beta-reader, .gemini/skills/beta-reader, .github/skills/beta-reader and .opencode/skills/beta-reader in your project.

What does Beta Reader need to run?

SKILL.md names no scripts, command-line tools or credentials: Beta Reader is instructions for the agent only.

Does Beta Reader access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Beta Reader safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Beta Reader use?

Beta Reader is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Beta Reader use?

About 2.4k tokens (SKILL.md is roughly 9.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.1k tokens, read only when the agent opens those files.

What are the alternatives to Beta Reader?

Skills that share tags, products or a category with Beta Reader: Story Multi-Perspective Review (zenstory-ai/oh-story-claudecode, 7.4k stars), Story Toolbox Router (zenstory-ai/oh-story-claudecode, 7.4k stars), Short Web Fiction Trend Scan (zenstory-ai/oh-story-claudecode, 7.4k stars) and InkOS Creative Harness (Narcooo/inkos, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Beta Reader?

felipelobomotta-blip (a GitHub user) maintains it in felipelobomotta-blip/book-genesis-studio, which has 139 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on September 22, 2026.

Source: felipelobomotta-blip/book-genesis-studio on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.