Book Writing
Plan, draft, and revise complete books with chapter architecture, voice consistency, and finish-ready revision workflows.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install openclaw-skills-book-writing
Repository
Skill path: skills/ivangdavila/book-writing
Plan, draft, and revise complete books with chapter architecture, voice consistency, and finish-ready revision workflows.
Open repositoryBest for
Primary workflow: Write Technical Docs.
Technical facets: Full Stack, Tech Writer.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: openclaw.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install Book Writing into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/openclaw/skills before adding Book Writing to shared team environments
- Use Book Writing for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
---
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.
| Topic | File |
|-------|------|
| Setup and integration | `setup.md` |
| Memory schema | `memory-template.md` |
| Book blueprint design | `blueprint.md` |
| Chapter drafting loop | `chapter-loop.md` |
| Revision and finish criteria | `revision-rubric.md` |
## 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 <slug>` 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`
---
## Skill Companion Files
> Additional files collected from the skill directory layout.
### _meta.json
```json
{
"owner": "ivangdavila",
"slug": "book-writing",
"displayName": "Book Writing",
"latest": {
"version": "1.0.0",
"publishedAt": 1772234895074,
"commit": "https://github.com/openclaw/skills/commit/062230f19664cdc087beecc638dff49026db7956"
},
"history": []
}
```