html-to-pdf
Render HTML (with CSS) to a PDF file. Trigger when the user wants to export a styled report, invoice, label, or any HTML/Jinja-rendered page to PDF. Uses WeasyPrint, which supports a meaningful subset of CSS Paged Media (page size, margins, headers/footers, page-break-before/after). Optional dependency — install via `pip install opensquilla[document-extras]` or `uv add weasyprint` because WeasyPrint pulls in native libraries (Pango, Cairo, fontconfig) that need OS-level packages.
Profile →npx skills add opensquilla/opensquilla --skill html-to-pdf --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# html-to-pdf Render HTML + CSS to PDF using WeasyPrint. Best for static report exports where the source already exists in HTML form (templates, dashboards, invoices). For programmatic PDF assembly from data structures, use the `pdf-toolkit` skill's reportlab path instead. ## Delivery rule First, use the available tool list for this session to choose the delivery path. If `write_file`, `edit_file`, `apply_patch`, or `execute_code` is available: - Build the `.pdf`, `.html`, or requested file in the active workspace using the workflow below. - Call `publish_artifact` for the final file before your final reply when that tool is available. - The examples and workflow steps later in this document apply. If none of those file-authoring tools are available: - Do not attempt to generate, save, or modify the final file. - Do not paste the full HTML/CSS source into chat as a substitute for delivering the file. - Ignore the Quick start and Workflow sections below; they do not apply when file authoring is unavailable. - Reply plainly: explain that the current session cannot create files, and offer to publish an existing file by path, describe the document contents in text, or continue in a fil
- Delivery rule
- Use cases
- Limitations
- Quick start
- CSS Paged Media support
- Cross-platform install hints
- macOS
- Debian/Ubuntu
- Windows
- Boundaries
python {baseDir}/scripts/render.py --html report.html --out report.pdf
python {baseDir}/scripts/render.py --html invoice.html --out invoice.pdf --page-size A4
brew install pango cairo gdk-pixbuf libffi
sudo apt-get install -y libpango-1.0-0 libpangoft2-1.0-0 \
libharfbuzz0b libfontconfig1What does the html-to-pdf skill do?
Render HTML (with CSS) to a PDF file. Trigger when the user wants to export a styled report, invoice, label, or any HTML/Jinja-rendered page to PDF. Uses WeasyPrint, which supports a meaningful subset of CSS Paged Media (page size, margins, headers/footers, page-break-before/after). Optional dependency — install via `pip install opensquilla[document-extras]` or `uv add weasyprint` because WeasyPrint pulls in native libraries (Pango, Cairo, fontconfig) that need OS-level packages.
How do I install it?
Run `npx skills add opensquilla/opensquilla --skill html-to-pdf --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From opensquilla/opensquilla, a repository with 6,515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.