AuthorKit

Publishing Pipeline · Free & Open Source

Your Obsidian vault,
print-ready.

AuthorKit is a free, open-source pipeline that turns an Obsidian vault into a print-ready book PDF. It typesets your Markdown through Quarto and Typst, with chapters opening on a recto, binding margins and blank versos without folios. It also reads your manuscript while you draft and points out structural problems before they reach a proof.

Each title needs one small book.yml file instead of its own build script. Novels, picture books and workbooks all come from the same tool.

While you write

Structure, charted
Charts your manuscript's pacing scene by scene and act by act, so you can see it at a glance. Word counts are taken from the text itself.
Measured against a shape
Compare that arc to a named structure: Freytag's Pyramid, or a rasa-cycle template for non-Western story structure. Mark where you meant the climax to be and see where it lands.
Continuity checks
Finds characters who are mentioned but have no note, acts and chapters that drift out of order, and scene files that sit in the folder but are missing from the index.
Script-agnostic linking
Links each character's first mention to their note. Each book lists the scripts it uses and which word endings still count as the same name, so a Gujarati book and an English book are set up differently without changing any code.
Prose, typeset
You write Markdown and the build typesets it: trim size and bleed, a wider gutter for the binding, chapters opening on a right-hand page, blank versos without a folio, and old-style figures. The default fonts come with Typst, so you don't need to install any.
Illustrated layout
A picture book places its own art and type per scene, in a Typst block that stays readable in Obsidian. Bleed is added when the PDF is built, on whichever edges each page needs.
Kindle from the same source
The ebook interior is built from the same scene files as the print PDF, so there is only one manuscript to keep up to date.
It asks first
Setup asks what kind of book you're making before it creates any files, because a novel and a picture book need very different page setups. A wrong answer still gives you a valid PDF, but of the wrong kind of book.

In Claude Code

/book-new
Sets up a new book vault. It asks for the title, format, manuscript status and where you'll publish, then creates the folders and files.
/book-audit-vault
Checks the vault is sound: book.yml valid, Story/Index.md and Characters/ present, and refreshes the structure chart.
/book-audit-manuscript
Checks the manuscript for characters without a note, acts and chapters out of order, and first mentions that should be linked.
/book-build
Builds the print PDF and prepares the Kindle interior from the same files.

Or without Claude Code

Everything above also runs as a plain command, so you can use the kit without Claude Code.

python3 authoring/cli.py init       # interview, then scaffold
python3 authoring/cli.py skeleton   # structure + pacing chart
python3 authoring/cli.py link       # first mentions -> character notes
python3 authoring/cli.py check      # continuity and unlisted scenes
python3 pipeline/build.py           # -> Deliver/<title>.pdf

It comes with two example vaults you can build straight away: a novel with nested folders and a picture book with a flat one. Both use public-domain text and together take up under 14 KB. The kit tests itself with 47 checks.

Install

/plugin marketplace add maulikmehta/obsidian-book-pipeline
/plugin install obsidian-book-pipeline@authorkit

Free, MIT licensed. Source on GitHub.

The tool is still being developed, so check your output before you send it to a distributor.

Requirements

  • Quarto, which turns .qmd files into Typst and then PDF
  • Python 3
  • ImageMagick, for cover cropping
  • A typeface of your choice, if you don’t want the default
AuthorKit™ is an initiative by Swati Joshi, who publishes 6 titles in 13 live editions on Amazon.com, Amazon.in, IngramSpark and Barnes & Noble, all built with this pipeline. It typesets a book you have already written and checks its structure. It doesn't write or edit your prose, and the pipeline itself doesn't use AI. Your cover artist, illustrator and designer still do their own work. If you want a quick way to publish a lot of books, this isn't it. Your manuscript never leaves your computer, unless you use the optional Claude Code plugin, which works under your own Claude account.

Thinking out loud

What are you fighting with?

Five picture books and a novella in, production has got easier, but only for those two kinds of book: spreads and bleed for one, chapter breaks and binding margins for the other. What I don't know is what everyone else is stuck on: activity books, poetry where the line breaks have to survive, cookbooks, non-Latin scripts, a trim size nobody stocks.

I'm working out whether to help other authors with this, and I'd rather build around what people actually get stuck on than what I assume. If that's you, tell me what format is giving you trouble.

Message me on Instagram