Skip to content
Back to skills

Book Writing

ASecurity

Plan, draft, and revise complete books with chapter architecture, voice consistency, and finish-ready revision workflows.

  • 17 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 6, 2026
content-marketingrustapisecurity

Works with

  • api

Security analysis

A100/100

Pro scans all 7 files and shows the line behind each finding

Scanned September 6, 2026

npx -y skills add clawic/skills --skill book-writing --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Book Writing?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Book Writing
[![Security: A β€” Skills Directory](https://www.skillsdirectory.com/api/skills/clawic-book-writing/badge)](https://www.skillsdirectory.com/skills/clawic-book-writing)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: Book Writing
slug: book-writing
version: 1.0.0
description: Plan, draft, and revise complete books with chapter architecture, voice consistency, and finish-ready revision workflows.
homepage: https://clawic.com/skills/book-writing
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
    displayName: Book Writing
---

## 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 `~/Clawic/data/book-writing/`. See `memory-template.md` for setup and status fields.

```
~/Clawic/data/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 `~/Clawic/data/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 `~/Clawic/data/book-writing/` for memory storage.
- Delete user writing without explicit confirmation.

## Related Skills
More Clawic skills, get them at https://clawic.com/skills/<slug> (install if the 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, star it: https://clawic.com/skills/book-writing
- Latest version: https://clawic.com/skills/book-writing

Files in this skill

  • SKILL.md4.2 KB
  • _meta.json176 B
  • blueprint.md1.1 KB
  • chapter-loop.md889 B
  • memory-template.md1.2 KB
  • revision-rubric.md948 B
  • setup.md1.6 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…