pdfcraft
Installation
SKILL.md
PdfCraft
Operate PdfCraft through its structured automation interfaces. Preserve the user's requested document and editing workflow.
References
PdfCraft documents automation in two bundled snapshots, captured from upstream on 2026-11-09:
- references/mcp.md — the MCP server: startup flags, tool surface, and file-access confinement. Source: PdfCraft MCP conventions.
- references/cli-batch.md —
pdfcraft-cli batchfor convert, OCR, and optimize over files and folders. Source: PdfCraft batch docs.
Both are distributed under the bundled MIT license. Relative links inside the snapshots resolve against https://github.com/storytold/pdfcraft/blob/main/docs/. The desktop control channel is described in the upstream README; discover installed commands and flags rather than borrowing schemas from other ArtCraft applications.
Select the surface
- MCP (headless, opt-in):
pdfcraft-cli mcp [--root DIR] [--compact] [--automation-read-root DIR] [--automation-write-root DIR]runs over stdin/stdout JSON lines, opens no port, and stops on EOF. It always runs in its own process; it never attaches to the desktop app. - Desktop control (live window): start
pdfcraft --control ~/.pdfcraft-control.jsonto let an agent see and operate the real interface — widget tree, clicks, typing, keys, commands, screenshots. Off by default, loopback only, and every connection must present the random token in that file. Keep the control file in a folder only you can write (never/tmp);pdfcraft-cli uirefuses symlinked or world-readable control files. Drive it withpdfcraft-cli ui --control <file> inspect|click|key|command|drag|screenshot|resize|focus|quit. - One-off file processing:
pdfcraft-cli batch(see the batch reference) and the CLI's other subcommands.