AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Reader Panel

skill-tchr-dev-autonovel-reader-panel · by tchr-dev

Run a 4-persona reader panel (editor, genre reader, writer, first reader) on the full novel. Spawns four subagents in parallel, each evaluating independently, then merges results into consensus + disagreement findings. Use during revision cycles to surface novel-level issues that per-chapter eval misses.

No reviews yet
0 installs
13 views
0.0% view→install

Install

$ agentstack add skill-tchr-dev-autonovel-reader-panel

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-tchr-dev-autonovel-reader-panel)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
3mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Reader Panel? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Reader panel

A reader panel evaluates the novel AS A WHOLE, not chapter by chapter. The disagreements between readers are where editorial decisions live.

Procedure

Step 1 — build the arc summary

If /arc_summary.md does not already exist (or is stale), generate it. The arc summary is what you hand to each persona — they don't read 80k words.

For each chapter, write:

## Ch N — [title]

OPENING (~150 words, lightly trimmed from the actual chapter open)
...

KEY BEATS:
- beat 1
- beat 2
- beat 3

KEY DIALOGUE (1-2 lines that capture the chapter's tone)

CLOSING (~100 words from the chapter's actual ending)

Concatenate all chapters into /arc_summary.md. Total target ~12,000-18,000 words for a 75k-word novel.

Step 2 — spawn four subagents in parallel

Use the Agent tool with one tool-use block containing four parallel calls:

| subagent_type | Persona | |---|---| | panel-editor | Senior fiction editor | | panel-genre-reader | Avid fantasy reader | | panel-writer | Published novelist | | panel-first-reader | Thoughtful general reader |

To each, pass:

  • The full content of /arc_summary.md inline in the prompt
  • A note that the novel is N chapters / W words
  • The JSON schema (in each agent's instructions, but reiterate it: the 10 questions)

Each agent returns JSON with the 10 questions answered.

Step 3 — merge

Save each persona's JSON to /edit_logs/reader_panel.json under readers..

For consensus detection across these questions: momentum_loss, cut_candidate, thinnest_character, worst_scene:

  1. Extract chapter numbers each persona mentions (re.findall(r'Ch(?:apter)?\s*(\d+)', answer, re.IGNORECASE)).
  2. For each chapter mentioned by any persona, list which personas flagged it and which didn't.
  3. Consensus item = 3-of-4 or 4-of-4 agreement. These are revision priorities.
  4. Disagreement item = 1-of-4 or 2-of-4. These are editorial calls — flag them but don't auto-act.

Write /edit_logs/reader_panel.json:

{
  "readers": {
    "editor": { /* the editor's JSON */ },
    "genre_reader": { /* ... */ },
    "writer": { /* ... */ },
    "first_reader": { /* ... */ }
  },
  "consensus_items": [
    {"question": "cut_candidate", "chapter": 14, "agreement": "4/4", "details": {...}}
  ],
  "disagreements": [
    {"question": "thinnest_character", "chapter": 8, "flagged_by": ["editor"], "not_flagged": ["genre_reader", "writer", "first_reader"]}
  ],
  "timestamp": "..."
}

Output to user

Print:

  • Each persona's would_recommend and best_scene answer (one line each)
  • All consensus items with the question and chapter
  • All disagreements with the split

Suggest: pass each consensus item to gen-brief to generate a revision brief, then gen-revision.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.