Knowledge Base Book Writer

Problem Solved

Knowledge bases often contain notes, cases, and documents scattered across files. Turning them into a book is not only a copywriting task; it requires structure, sufficient length, case support, and publisher-level layout. The xieshu skill targets that workflow, with a hard requirement of at least 100,000 Chinese characters in the main text before delivery.

How It Works

The skill runs through four stages:
- Read the knowledge base: it scans sources with search(source='kb'), fetches key documents with fetch(type='media_id'), and saves distilled arguments, data, and reusable excerpts to book-materials.md.
- Plan the outline: it proposes book title options, chapter titles, content scope, and length allocation in book-outline.md; chapter writing starts only after explicit user confirmation.
- Write chapters: for each chapter, it retrieves relevant material, adds knowledge-base or web research if needed, and saves the draft as chapter-XX.md with progress updates.
- Integrate and deliver: it merges all chapters and produces a 16-kai, publisher-formatted full-book.docx, including page size, margins, fonts, line spacing, headings, page numbers, cover, table of contents, code blocks, and tables.

Boundaries

It is best suited to knowledge-base projects that already contain substantive material. If sources are thin, the skill is expected to compensate through additional search, expanded cases, or practical chapters to meet the length floor. Outline, chapter, and style changes can be made in later rounds, but the Word document must be regenerated after edits. For strict factual verification, academic citation, or formal publishing review, treat the output as an editable manuscript rather than a final version.