markdown-to-booklisted

Bundle a COLLECTION of markdown files (a docs folder, numbered chapters, a research series) into one book published in three lockstep editions sharing one basename: a single-file .md agent edition with provenance frontmatter (the context handoff for another AI agent), an .epub reading edition (Kindle/TTS, via the markdown-to-epub recipe), and a .pdf print edition (via the markdown-to-pdf recipe). Use whenever the user wants to share a multi-file markdown corpus as ONE artifact - with their team, their Kindle, or another agent. Triggers: 'bundle these chapters', 'make a book from this folder', 'turn this folder into one file', 'context bundle', 'single file for my agent', 'markdown to context', 'markdown to agent', 'share this with an agent at work', 'rebuild the book', 'the three editions', 'epub and pdf and markdown of this folder'. Also use when a previously built book's source chapters changed and the editions must be rebuilt in lockstep. NOT for converting one markdown file (use markdown-to-epub or markdo
dzivkovi/claude-skills · ★ 0 · Data & Documents · score 61

Install: claude install-skill dzivkovi/claude-skills

# markdown-to-book One source folder of markdown chapters, three published editions, one basename: | Edition | Audience | What makes it that edition | |---|---|---| | `.md` | An AI agent (context handoff) | Single concatenated file, provenance frontmatter, Mermaid kept as live fences (machine-readable source beats a picture) | | `.epub` | A human reading or listening (Kindle, TTS) | Cover, combined TOC, Mermaid rendered to PNG | | `.pdf` | A human printing or skimming | Page/version/date stamps, Mermaid rendered as vector | They are editions of one book, never three documents. **The lockstep rule: any edit to a source chapter invalidates all three; rebuild all three in the same session, or say plainly which ones are stale.** Filenames never carry version suffixes in a repo - git history is the version axis; note content changes concisely in the intro's "Edition notes" block instead. Version-suffixed names belong only in throwaway locations (Downloads) where generations coexist as loose files. ## Step 0 - scope check and dependencies A single markdown file needs no bundling: hand it to `markdown-to-epub` or `markdown-to-pdf` directly and stop here. This skill earns its keep when there are multiple files whose value depends on order and togetherness. **Sibling-skill dependency (check FIRST):** the EPUB and PDF steps call the `markdown-to-epub` and `markdown-to-pdf` skills' own scripts and stylesheet (`make_cover.py`, `epub.css`, `print_markdown.py`). Verify both skill fol