beta-reader

Simulate three reader personas to diagnose manuscript engagement and structural issues.

92|28|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/felipelobomotta-blip/book-genesis-v4 --skill beta-reader-felipelobomotta-blip
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beta-reader
Source: https://github.com/felipelobomotta-blip/book-genesis-v4/tree/main/skills/beta-reader
Command: npx skills add https://github.com/felipelobomotta-blip/book-genesis-v4 --skill beta-reader-felipelobomotta-blip

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill helps you diagnose weaknesses in a manuscript by simulating three reader mindsets with different tolerances, priorities, and failure points so you can fix engagement and structural issues before editors or real readers do.

Core Features & Use Cases

  • Three distinct reader personas: The Devorador (pacing/flow), the Crítico (depth/coherence/originality), and the Hostil (logic holes/credibility/AI-scent) each produce targeted findings.
  • Concrete diagnostic outputs: Each persona reports an abandonment point, top problems with quoted evidence, top strengths with quoted evidence, and what feels missing.
  • Cross-diagnosis logic: Aggregates the three reports to classify issues as critical/real/preferential and identifies preserve-worthy strengths.

Quick Start

Use the beta-reader skill on one chapter, part, or the full manuscript and ask it to output the 3 persona reports plus the prioritized diagnosis and recommendations.

Frequently Asked Questions about beta-reader

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get beta reader feedback on a manuscript before submission?

Manuscript beta reading feedback is generated by simulating three distinct reader personas to identify pacing issues, logic holes, and engagement drops. The process outputs persona-specific abandonment points and a cross-diagnostic table to guide structural revisions before editor submission.

What is structural criticism and how does it find manuscript weaknesses?

Structural criticism identifies manuscript weaknesses by simulating multiple reader mindsets to detect pacing flaws, logic holes, and credibility drops. It classifies detected issues by severity and highlights engagement strengths to preserve during book drafting revisions.

Can I use reader simulation to check pacing and flow in a book draft?

Yes, reader simulation checks pacing and flow by deploying a specialized persona that monitors narrative momentum and structural coherence. It reports specific abandonment points and extracts quoted evidence to pinpoint exactly where book drafting pacing fails.

How do I validate whether manuscript revisions fixed previous editorial evaluation issues?

Validate manuscript revisions by re-running the reader simulation on updated text to check if previous abandonment points disappear. This editorial evaluation detects whether structural changes resolved pacing issues or introduced new logic holes and credibility drops.

What does a cross-persona diagnostic table show for manuscript review?

A cross-persona diagnostic table aggregates structural criticism from all simulated readers to classify manuscript issues by severity. It maps shared abandonment points and pacing failures, providing a calibrated report that distinguishes critical flaws from preferential adjustments.