reader-experience-edit
Audit and revise practical nonfiction drafts for reader experience, value pacing, front-loaded insight, value-per-page, boredom, and beta-readiness. Use when editing, restructuring, shortening, or reviewing a book, guide, manual, course-like manuscript, or long-form educational draft so readers receive useful value quickly and keep reading.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- reader-experience-edit
- license
- MIT
- metadata
- { "tags": "writing,books,nonfiction,editing,reader-experience", "version": "0.1.0", "category": "Writing", "displayName": "Reader Experience Edit" }
- description
- Audit and revise practical nonfiction drafts for reader experience, value pacing, front-loaded insight, value-per-page, boredom, and beta-readiness. Use when editing, restructuring, shortening, or reviewing a book, guide, manual, course-like manuscript, or long-form educational draft so readers receive useful value quickly and keep reading.
- compatibility
- Codex, Claude Code, and other Agent Skills-compatible clients.
02 资源文件 5
- 参考文档references/core/checklist.md2.1 KB
- 参考文档references/core/examples.md2.4 KB
- 参考文档references/core/knowledge.md3.5 KB
- 参考文档references/core/rules.md2.9 KB
- 参考文档workflows/audit-manuscript.md2.2 KB
03 SKILL.md 正文
Reader Experience Edit
Core Lens
Treat reader experience as value received over time spent. Practical nonfiction does not keep readers engaged through suspense; it keeps them engaged by regularly delivering the outcome promised by the book.
Use this skill to diagnose and improve:
- Slow starts.
- Long stretches of theory before payoff.
- Low value-per-page.
- Sections whose value is unclear.
- Drafts that need to be coherent enough for beta readers, not polished enough for publication.
Reference Routing
| Need | Read |
|---|---|
| Core concepts and terminology | references/core/knowledge.md |
| Revision rules and decision criteria | references/core/rules.md |
| Before/after patterns | references/core/examples.md |
| Fast audit checklist | references/core/checklist.md |
| Step-by-step manuscript audit | workflows/audit-manuscript.md |
Workflow
1. Anchor On The Promise
Identify:
- Target reader.
- Book promise.
- First meaningful piece of value.
- What the reader should be able to do, decide, or understand after each major section.
If the promise is unclear, use book-toc-lab before editing the manuscript.
2. Create A Value Map
Build a table:
Section | Word count | Reader takeaway | Value type | Risk
Use it to find:
- Slow start: too many words before first value.
- Long slog: back-to-back sections without strong takeaways.
- Fluff: high word count relative to reader value.
3. Front-Load Value
Look for ways to deliver the first useful result earlier:
- Cut front matter.
- Insert real value into theory sections.
- Start with the main insight, tool, checklist, example, or result.
- Move background after the reader has a reason to care.
4. Increase Value-Per-Page
Prefer deletion before addition.
- Cut anything outside the target reader's scope.
- Replace general motivation with concrete examples.
- Compress explanations that do not change reader behavior.
- Save deleted material in a separate cutting-room-floor note when useful.
5. Prepare For Beta Readers
Do not aim for perfect prose yet. Aim for a draft that is coherent enough for motivated readers to identify real problems.
Return:
- Main reader-experience diagnosis.
- Value map or section-by-section risk table.
- Highest-leverage cuts, moves, and rewrites.
- Revised opening or TOC recommendations when relevant.
- Beta-readiness note: what must be fixed before readers see it.
Quality Bar
Recommendations should be structural and specific. Prefer "move this section after X", "cut this setup", or "turn this theory into a worked example" over generic writing advice.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.