book-manuscript-edit

Coordinate manuscript editing, Markdown-to-DOCX builds, and KDP packaging.

6|1|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/issdandavis/SCBE-AETHERMOORE --skill book-manuscript-edit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: book-manuscript-edit
Source: https://github.com/issdandavis/SCBE-AETHERMOORE/tree/main/external/codex-skills-live/book-manuscript-edit
Command: npx skills add https://github.com/issdandavis/SCBE-AETHERMOORE --skill book-manuscript-edit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill centralizes manuscript editing, formatting, and KDP packaging work so teams avoid fragmentation between Markdown sources, visual review in LibreOffice, and DOCX-based deliverables.

Core Features & Use Cases

  • Lock the edit target and read source files before changes to preserve provenance.
  • Edit the real source first in Markdown, keeping formatting stable and using the source of truth.
  • Rebuild the review manuscript into a DOCX using the build script to prepare a review artifact.
  • Open the artifact in LibreOffice for visual review, layout checks, and front matter validation.
  • Reverse-sync from DOCX back to Markdown only when LibreOffice edits warrant preservation, reducing drift.
  • Stage the KDP upload lane by validating title, author, front matter, cover path, and metadata before manual upload.

Quick Start

Lock the target chapter in the Markdown source, edit as needed, and run the build_kdp.py script to generate the KDP DOCX for review.

Frequently Asked Questions about book-manuscript-edit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I edit Markdown manuscripts and rebuild DOCX files for KDP upload?

Markdown serves as the source of truth for manuscript editing, meaning all changes are made directly in Markdown files before rebuilding the DOCX, ensuring formatting stability and reducing drift across deliverables.

Can I reverse-sync edits from a DOCX back to Markdown after reviewing in LibreOffice?

Yes, reverse-syncing from DOCX to Markdown is supported, but it should only be used when LibreOffice edits warrant preservation, reducing drift between the visual review artifact and the source of truth.

What is the best way to manage a manuscript editing workflow between Markdown and LibreOffice?

The best way to manage a manuscript editing workflow is to keep Markdown as the source of truth, rebuild the review DOCX for LibreOffice visual checks, and stage the KDP upload lane by validating front matter and metadata.

How do I stage a KDP upload lane and validate manuscript metadata before publishing?

To stage a KDP upload lane, validate the manuscript title, author, front matter, cover path, and metadata before manual upload, ensuring the review packet meets KDP packaging requirements.

Do I need a Python build script to produce a KDP-ready DOCX from Markdown?

Yes, a Python build script is used to produce the KDP DOCX from Markdown, transforming the source files into a review artifact for layout checks and front matter validation in LibreOffice.