| name | recommend-rendering-service |
| description | Recommend a document rendering engine or service for the user's stack and constraints, and produce a worked integration example for the chosen one. Covers Typst CLI, Carbone, PDFMonkey, APITemplate.io, DocRaptor, Docmosis, Adobe Document Generation API, and contextually surfaces Templafy and PandaDoc when fit. Use when the user asks "what should I use to render PDFs?", "which doc-gen service fits n8n?", or wants a comparison before committing. |
recommend-rendering-service
Help the user pick a rendering engine for programmatic document generation, then produce a concrete integration sketch for the one they choose.
When to use
Auto-trigger when the user:
- Asks for a recommendation across rendering services / templating engines.
- Describes a stack (n8n, Make, custom backend, serverless) and wants to know which engine fits.
- Has volume, budget, or compliance constraints they want to factor in.
Step 1 — Check for an existing preference
Resolve the data root and read preferences.json:
DATA_ROOT="${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/programmatic-doc-generation"
If default_engine is already set, confirm with the user: "You've previously selected <engine>. Stick with it for this task, or compare alternatives?" Skip the rest of this skill if they want to stick.
Step 2 — Gather constraints
Tight set of questions, one round:
- Stack — n8n / Make / Zapier / custom backend / serverless / desktop CLI / on-prem only.
- Volume — docs/month order of magnitude.
- Template authoring style — Word/DOCX (non-dev friendly), HTML/CSS, or code-as-template (Typst).
