book-toc-lab
Design and pressure-test useful nonfiction book promises, scopes, recommendation loops, and takeaway-first tables of contents before drafting. Use when planning, outlining, scoping, restructuring, validating, or testing a practical book, guide, manual, course-like book, or other reader-outcome-focused long-form nonfiction.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- book-toc-lab
- license
- MIT
- metadata
- { "tags": "writing,books,nonfiction,outlining,toc", "version": "0.1.0", "category": "Writing", "displayName": "Book TOC Lab" }
- description
- Design and pressure-test useful nonfiction book promises, scopes, recommendation loops, and takeaway-first tables of contents before drafting. Use when planning, outlining, scoping, restructuring, validating, or testing a practical book, guide, manual, course-like book, or other reader-outcome-focused long-form nonfiction.
- compatibility
- Codex, Claude Code, and other Agent Skills-compatible clients.
02 资源文件 7
- 资产文件assets/app-icon.png45.0 KB
- 参考文档references/core/checklist.md2.2 KB
- 参考文档references/core/examples.md2.3 KB
- 参考文档references/core/knowledge.md3.8 KB
- 参考文档references/core/rules.md3.1 KB
- 参考文档workflows/design-toc.md4.0 KB
- 参考文档workflows/validate-toc.md2.6 KB
03 SKILL.md 正文
Book TOC Lab
Treat a useful nonfiction book as a problem-solving product for a specific reader. The table of contents is the product design, not a decorative outline. Build and test the promise, scope, recommendation loop, and TOC before drafting so the manuscript has a clear job and useful progression.
Use this skill to produce or improve a book plan that answers:
- Who is this book for?
- What painful or valuable problem does it help them solve?
- What should be different for the reader after each chapter?
- What does the book deliberately leave out?
- Why would a satisfied reader recommend it to a specific person in a specific situation?
Resource Routing
Load only the files needed for the task:
| Need | Read |
|---|---|
| Core model, DEEP, promise, scope, recommendation loop | references/core/knowledge.md |
| Concrete planning and validation rules | references/core/rules.md |
| Before/after examples for scope and TOC titles | references/core/examples.md |
| Quick planning and review checklist | references/core/checklist.md |
| Step-by-step TOC design before drafting | workflows/design-toc.md |
| Step-by-step TOC validation with readers | workflows/validate-toc.md |
Fast Workflow
- Lock the reader promise before outlining.
- Define in-scope, out-of-scope, prerequisites, and depth lines.
- Write the recommendation story: trigger, recommender, recommended reader, and why this book is the obvious fit.
- Draft chapters as reader takeaways, not author topic buckets.
- Order chapters by reader progress: orientation, foundation, action, judgment, and integration.
- Pressure-test every chapter against the promise, reader outcome, missing steps, boredom risk, confusion risk, skepticism, and recommendability.
- Validate the TOC before drafting when practical.
Output Format
When asked to create or improve a TOC, return:
- Book brief: reader, problem, promise, scope, out-of-scope.
- Recommendation story: trigger, recommender, recommended reader, why this book.
- Recommended TOC with chapter-level reader problems and takeaways.
- Reader journey notes explaining the order.
- Risk list: missing prerequisites, vague chapters, likely confusion, likely boredom.
- Validation plan: 3-7 concrete ways to test the TOC before drafting.
Quality Bar
A good TOC should feel useful even before the book exists. A reader should be able to scan it and understand what the book helps them accomplish, whether it is for them, and why the chapter sequence makes sense.
Do not optimize for literary cleverness before usefulness. Clever titles are acceptable only after the reader promise and chapter takeaways are obvious.
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.