ai-pdf-builder

The local generation path is the part worth having, because it produces a document without sending your draft to a third party and without a per-document cost. The enhance and summarize commands are sensible conveniences, and content sanitisation suggests the authors have met the messy-output problem. The caveat is the same one that applies to every document generator aimed at legal templates: a generated agreement is a draft, and relying on it without review by someone qualified is a real risk rather than a stylistic preference. Also verify the local toolchain prerequisites before the first run, since the path that needs a typesetting stack fails in a way that looks like a content problem. For internal memos and whitepapers the trade-off is mild; for anything that gets signed, treat the output as a starting point only.

Use case: Producing internal memos, whitepapers or draft documents locally without external generation costs.

# Generate with the model, render locally, review like a contract This skill turns a prompt into a formatted document — whitepapers, memos, term sheets, agreements — with two rendering paths: a local path using pandoc and a LaTeX distribution, and a hosted path that needs nothing installed. The choice between them is really a choice about where the content and the dependency live. ## Install the local renderer once ```bash brew install pandoc brew install --cask basictex ``` The local path is free and unlimited, which is the right default for anything sensitive, but a LaTeX distribution is a large install. Do it once in the image rather than per run, and treat its presence as a precondition for scheduled jobs. ## Separate content from rendering The content commands improve or condense a document; the renderer turns structured content into a PDF. Run them as separate steps so a rendering failure does not force a regeneration, which costs a model call and can produce different text. ## Sanitisation is cleanup, not review Automatic content sanitisation removes generation artefacts. It does not check whether the sentence you are about to sign is true, and it leaves placeholders in place. Everything in the output has to be read by a human before it goes anywhere. ## Legal templates especially For agreements, a generated document is a first draft of structure, never a source of legal position. Keep the template's variable fields explicit and small so a reviewer can see exactly what the model chose versus what the template fixed.