什么是 书籍创作？

书籍创作技能是一个专门的工作流，专为需要专业级稿件结构的作者和内容创作者设计。它将 AI 智能体转化为成熟的写作伙伴，能够管理复杂的章节架构，保持叙事连贯性，并执行多轮修订。通过在 Openclaw Skills 生态系统中使用此工具，用户可以从模糊的前提过渡到准备就绪的稿件，而不会丢失其独特的文风或观点。

该技能优先考虑书籍的架构完整性，确保每一章都服务于特定的读者成果。它利用本地记忆来跟踪项目状态、文风档案和下一步行动，是任何认真对待高质量书籍项目的人员必备的工具。

下载入口:https://github.com/openclaw/skills/tree/main/skills/ivangdavila/book-writing

安装与下载

1. ClawHub CLI

从源直接安装技能的最快方式。

2. 手动安装

将技能文件夹复制到以下位置之一

优先级：工作区 > 本地 > 内置

3. 提示词安装

将此提示词复制到 OpenClaw 即可自动安装。

书籍创作 应用场景

• 规划一本具有明确读者转化承诺的新非虚构书籍。
• 在保持一致的角色语调和视角的同时起草小说章节。
• 通过结构化的逐轮日志管理大规模的稿件修订。
• 为长篇内容制定动态蓝图，以确保全局连贯性。
• 在过程早期发现结构性风险，如节奏漏洞或冗余章节。

1. 初始化本地记忆环境以建立文风偏好和稿件状态。
2. 在开始任何大规模起草之前，定义书籍承诺、受众和核心转化目标。
3. 在本地目录中创建动态蓝图，规划候选标题、章节地图和故事素材。
4. 执行专注于具体读者成果而非简单字数的章节级起草循环。
5. 进行结构化的修订轮次，侧重于逻辑、叙事连续性、清晰度，最后是润色。
6. 在每次会话后更新热记忆，记录精确的下一步行动以保持项目进度。

书籍创作 配置指南

要开始使用此技能，您必须初始化本地工作空间以捕获激活偏好和记忆设置。

1. 安装技能，然后阅读设置指南：

# 访问初始化指南
cat setup.md

2. 为您的稿件创建必要的目录结构：

mkdir -p ~/book-writing/chapters ~/book-writing/revisions ~/book-writing/archive

3. 根据提供的模板初始化记忆文件，开始跟踪您的书籍承诺和文风档案。

书籍创作 数据架构与分类体系

该技能在 ~/book-writing/ 目录中本地组织数据，以确保隐私和跨会话的持续上下文。它使用分层记忆系统：

name: Book Writing
slug: book-writing
version: 1.0.0
homepage: https://clawic.com/skills/book-writing
description: Plan, draft, and revise complete books with chapter architecture, voice consistency, and finish-ready revision workflows.
changelog: Initial release with end-to-end book planning, drafting, and revision workflows that preserve voice and narrative coherence.
metadata: {"clawdbot":{"emoji":"??","requires":{"bins":[]},"os":["linux","darwin","win32"]}}

Setup

On first use, read setup.md to initialize local memory and capture activation preferences.

When to Use

Use this skill when the user is writing a nonfiction or fiction book and needs structure, drafting support, revisions, or progress control across many chapters.

Architecture

Working memory lives in ~/book-writing/. See memory-template.md for setup and status fields.

~/book-writing/
├── memory.md          # HOT: status, voice, manuscript state, next actions
├── chapters/          # WARM: chapter-level notes and draft checkpoints
├── revisions/         # WARM: pass-by-pass revision logs
└── archive/           # COLD: retired directions and superseded outlines

Quick Reference

Use these files progressively to keep runtime context focused and avoid loading unnecessary detail.

Core Rules

1. Lock the Book Promise Before Drafting

Define audience, core promise, transformation, and scope before generating large text blocks. If these are unclear, pause drafting and clarify first.

2. Keep a Living Book Blueprint

Use blueprint.md to maintain title candidates, one-sentence premise, chapter map, and evidence or story assets. Update this blueprint whenever the direction changes.

3. Write by Chapter Outcomes, Not Word Count

Each chapter must deliver one concrete outcome for the reader. Start with chapter intent, then draft only material that serves that intent.

4. Preserve Voice and POV Consistency

Track voice profile in memory and enforce consistent point of view, tense, reading level, and sentence rhythm across chapters.

5. Run Structured Revision Passes

Revise in separate passes: structure, argument or narrative continuity, clarity, and line polish. Do not mix all passes at once.

6. Surface Risks Early

Flag weak logic, redundant chapters, unresolved promises, and pacing holes as soon as they appear. Propose fixes with concrete rewrite options.

7. Always End With the Next Smallest Action

After each interaction, leave a precise next step the user can execute immediately, such as chapter brief approval, scene rewrite, or revision pass target.

Common Traps

• Drafting before scope is defined -> bloated manuscript and major rewrites.
• Treating every chapter the same -> flat pacing and repetitive structure.
• Line editing too early -> local polish over global coherence.
• Changing voice mid-book -> reader trust drops quickly.
• Ignoring chapter outcomes -> chapters feel busy but non-essential.

Security & Privacy

Data that stays local:

• Project memory in ~/book-writing/.
• Chapter and revision notes created during sessions.

Data that leaves your machine:

• None by default.

This skill does NOT:

• Send manuscript data to external APIs.
• Access files outside ~/book-writing/ for memory storage.
• Delete user writing without explicit confirmation.

Related Skills

Install with clawhub install if user confirms:

• writing — voice adaptation and writing preference memory.
• writer — anti-robotic writing patterns and rhythm control.
• write — general-purpose drafting support for fast composition.
• article — long-form article structuring and editorial flow.
• content-marketing — audience-driven messaging and conversion framing.

Feedback

• If useful: clawhub star book-writing
• Stay updated: clawhub sync