book-swarm-panel
Use when a book project needs MiroFish-style simulated reader swarms, niche reader panels, public-opinion simulation, launch reaction testing, cultural/sensitivity risk scouting, agent interviews, review heatmaps, or revision tickets from many fictional readers. Use for requests mentioning simulated readers, public opinion, BookTok/Goodreads/Reddit/Twitter reaction, niche specialists, 20+ agents, crowd response, market reaction, or "MiroFish for books".
felipelobomotta-blip · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add felipelobomotta-blip/book-genesis-studio --skill book-swarm-panel技能说明
name: book-swarm-panel description: Use when a book project needs MiroFish-style simulated reader swarms, niche reader panels, public-opinion simulation, launch reaction testing, cultural/sensitivity risk scouting, agent interviews, review heatmaps, or revision tickets from many fictional readers. Use for requests mentioning simulated readers, public opinion, BookTok/Goodreads/Reddit/Twitter reaction, niche specialists, 20+ agents, crowd response, market reaction, or "MiroFish for books".
Book Swarm Panel
Book Swarm Panel runs a clean-room, book-specific swarm simulation inspired by MiroFish architecture. It creates many fictional readers, lets cohorts react to manuscript/package inputs, interviews selected agents, and writes durable evaluation artifacts.
It does not certify cultural approval, publication readiness, or bestseller odds. Simulated readers are diagnostic proxies.
When To Use
Use this skill for:
- simulated reader panels larger than normal beta reads
- niche/sensitivity-risk scouting before human consultants
- public-opinion tests for a manuscript, premise, cover copy, query, launch angle, or controversy
- BookTok/Goodreads/Reddit/Twitter-style reaction forecasts
- testing whether the book is being framed wrong
- generating heatmaps and revision tickets for
book-editor - re-running a post-revision panel with comparable calibration
Do not use this as a replacement for paid sensitivity readers, legal review, factual consultants, or human beta readers.
Output Location
Always write durable files.
Default run folder:
<project>/evaluations/book-swarm/<YYYY-MM-DD>-<run-slug>/
persona-roster.json
sample-map.md
cohort-reports.md
interviews.md
public-opinion-report.md
risk-heatmap.md
revision-tickets.md
score-calibration.md
SUMMARY.md
If no project folder exists, create evaluations/book-swarm/ near the provided manuscript.
Core Rule
Separate these claims:
- Simulated signal: useful hypothesis from fictional readers.
- Editorial judgment: craft/market interpretation by the agent running the skill.
- Human validation needed: anything involving lived culture, religion, trauma, law, medicine, or protected communities.
Never phrase simulated niche approval as real community approval.
Workflow
-
Load context
- Read
PROJECT_STATE.yaml,ASSUMPTIONS.md,foundation/positioning.md,research/market-research.md, previousevaluations/*.md, and manuscript chapters when available. - If package testing, also read logline, query, synopsis, cover copy, cover brief, and launch materials.
- Read
-
Choose mode
reader-swarm: broad beta reaction.niche-risk: cultural, religious, professional, geopolitical, or domain risk.public-opinion: social reaction to premise, excerpts, controversy, package, or launch angle.package-reaction: agent/editor/bookseller/reader reaction to query, copy, comps, cover, metadata.post-revision: compare current run against earlier score using same calibration.hybrid: combine modes when user asks for an aggressive market-level pass.
-
Build sample map
- For manuscripts >= 60k words, use stratified sampling unless user asks for full read.
- Always include first chapter, final chapter, climax, weakest flagged chapters, strongest flagged chapters, and any revised chapters.
- Record chapters fully read, partially read, and not read.
-
Generate persona roster
- Create 12-80 agents by default.
- For public opinion, use 40-250 short personas if feasible.
- Assign each persona: cohort, taste, expertise, tolerance, bias, trigger points, social behavior, likely abandon threshold, influence weight.
-
Run cohort evaluations
- Each cohort reports abandon point, confusion, delight, objection, shareability, rating, and evidence.
- Specialist/niche cohorts report
PASS,FLAG, orBLOCK, with line or scene evidence.
-
Simulate public reaction when requested
- Model 3-5 waves: initial hook, controversy, defense, backlash, stabilization.
- Track what spreads, what gets misread, who defends the book, who attacks it, and which framing reduces harm.
-
Interview selected agents
- Pick agents with strongest love, strongest rejection, most useful niche concern, and most representative middle response.
- Ask why they reacted that way and what change would move rating.
-
Synthesize
- Produce
risk-heatmap.md,revision-tickets.md, calibrated scores, andSUMMARY.md. - Mark every issue as
FIX,INVESTIGATE,IGNORE, orHUMAN-VALIDATE.
- Produce
Default Cohorts
Use only cohorts relevant to the book.
- Literary craft reader: prose, subtext, theme, memorability.
- Genre devourer: pace, hooks, abandon points, emotional payoff.
- Hostile continuity reader: logic, causality, timelines, contradictions.
- Anti-AI reader: synthetic phrasing, symmetry, over-explanation, empty abstraction.
- Literary agent: category, query hook, comps, submission risk.
- Acquiring editor: editorial labor, list fit, manuscript ceiling.
- Bookseller/category buyer: shelf fit, cover/copy promise, hand-sell angle.
- Target reader: desire, readability, recommendation likelihood.
- Non-target skeptic: where book repels wrong audience.
- Public reviewer: likely Goodreads/Amazon review language.
- BookTok/short-form reader: quotability, aesthetic hook, controversy.
- Reddit-style longform commenter: objections, lore analysis, argument threads.
- Niche/sensitivity proxy: cultural, religious, professional, or lived-experience risks.
Persona Schema
Use this shape in persona-roster.json:
{
"id": "agent_001",
"cohort": "niche-risk",
"name": "fictional persona label, not real person",
"background": "specific but fictional",
"taste": ["what they love"],
"intolerances": ["what makes them reject"],
"expertise_scope": "what they can evaluate",
"cannot_validate": "what still requires a human
阅读完整来源 ↗