explainx.ainewsletter3.4k
Frontend

html-to-pdf▌

aviz85/claude-skills-library · updated Jun 2, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/aviz85/claude-skills-library --skill html-to-pdf
0 commentsdiscussion
summary

Pixel-perfect HTML to PDF conversion with automatic RTL and Hebrew language support.

  • ›Renders using Chrome headless engine with full CSS3/HTML5 support, including Flexbox, Grid, custom fonts, and JavaScript execution
  • ›Automatic right-to-left direction detection for Hebrew, Arabic, and other RTL languages; includes --rtl flag for forced RTL mode
  • ›Configurable page formats (A4, Letter, Legal, A3, A5), orientation, margins, scale, and optional headers/footers
  • ›Requires one-time npm setup
skill.md

HTML to PDF Converter

Pixel-perfect HTML to PDF conversion using Puppeteer (Chrome headless). Provides excellent support for Hebrew, Arabic, and other RTL languages with automatic direction detection.

Why Puppeteer?

  • Pixel-perfect rendering: Uses actual Chrome engine
  • Full CSS3/HTML5 support: Flexbox, Grid, custom fonts, backgrounds
  • JavaScript execution: Renders dynamic content
  • Automatic RTL detection: Detects Hebrew/Arabic and sets direction
  • Web font support: Loads custom fonts properly

Auto-Fit (Built-in, No Flag Needed)

The script automatically handles content overflow:

  • Small overflow (up to ~18%) → auto-shrinks font size to fit the page
  • Large content → flows cleanly across multiple pages with smart page-break rules (no cutting headers, table rows, or images in half)
  • Fits perfectly → does nothing

This runs automatically on every PDF generation. No flags needed.

CRITICAL: Fit Content to Single Page

Backgrounds on html or body cause extra pages! Put backgrounds on a container element instead:

@page { size: A4; margin: 0; }

html, body {
  width: 210mm;
  height: 297mm;
  margin: 0;
  padding: 0;
  overflow: hidden;
  /* NO background here! */
}

.container {
  width: 100%;
  height: 100%;
  padding: 20mm;
  box-sizing: border-box;
  background: linear-gradient(...); /* Background goes HERE */
}

Common causes of extra pages:

  1. Background on html/body - always put on .container instead
  2. Content overflow - use overflow: hidden
  3. Margins/padding pushing content out

Tips:

  • Use --scale=0.75 --margin=0 if content still overflows
  • For landscape: use --landscape

Setup (One-time)

Before first use, install dependencies:

cd ~/.claude/skills/html-to-pdf && npm install

Quick Usage

Convert local HTML file:

node ~/.claude/skills/html-to-pdf/scripts/html-to-pdf.js input.html output.pdf

Convert URL to PDF:

node ~/.claude/skills/html-to-pdf/scripts/html-to-pdf.js https://example.com page.pdf

Hebrew document with forced RTL:

node ~/.claude/skills/html-to-pdf/scripts/html-to-pdf.js hebrew.html hebrew.pdf --rtl

Pipe HTML content:

echo "<h1>שלום עולם</h1>" | node ~/.claude/skills/html-to-pdf/scripts/html-to-pdf.js - output.pdf --rtl

Options Reference

Option Description Default
--format=<format> Page format: A4, Letter, Legal, A3, A5 A4
--landscape Use landscape orientation false
--margin=<value> Set all margins (e.g., "20mm", "1in") 20mm
--margin-top=<value> Top margin 20mm
--margin-right=<value> Right margin 20mm
--margin-bottom=<value> Bottom margin 20mm
--margin-left=<value> Left margin 20mm
--scale=<number> Scale factor 0.1-2.0 1
--background Print background graphics true
--no-background Don't print backgrounds -
--header=<html> Header HTML template -
--footer=<html> Footer HTML template -
--wait=<ms> Wait time for fonts/JS 1000
--rtl Force RTL direction auto-detect
--expect-pages=<N> Expected page count (warns if different) 1
--no-page-check Disable page count warning -

Automatic Overflow Detection

The script automatically checks page count after generating the PDF. By default, it expects 1 page and warns if the output has more:

⚠️  WARNING: PAGE OVERFLOW DETECTED!
   Expected: 1 page(s)
   Actual:   2 page(s)

   Fix: Reduce content, margins, or font sizes in HTML
   Use --no-page-check to disable this warning

Usage:

  • Default: expects 1 page, warns on overflow
  • --expect-pages=3: expects 3 pages (for multi-page documents)
  • --no-page-check: disables the check entirely

Note: Requires pdfinfo to be installed (part of poppler-utils). If not available, the check is silently skipped.

Examples

Basic conversion:

node ~/.claude/skills/html-to-pdf/scripts/html-to-pdf.js report.html report.pdf

Letter format with custom margins:

node ~/.claude/skills/html-to-pdf/scripts/html-to-pdf.js doc.html doc.pdf --format=Letter --margin=1in

Hebrew invoice:

node ~/.claude/skills/html-to-pdf/scripts/html-to-pdf.js invoice-he.html invoice.pdf --rtl

Landscape presentation:

node ~/.claude/skills/html-to-pdf/scripts/html-to-pdf.js slides.html slides.pdf --landscape --format=A4

No margins (full bleed):

node ~/.claude/skills/html-to-pdf/scripts/html-to-pdf.js poster.html poster.pdf --margin=0

Hebrew/RTL Best Practices

For best Hebrew rendering in your HTML:

  1. Set lang attribute: <html lang="he" dir="rtl">
  2. Use UTF-8: <meta charset="UTF-8">
  3. CSS direction: Add direction: rtl; text-align: right; to body
  4. Fonts: Use web fonts that support Hebrew (Noto Sans Hebrew, Heebo, Assistant)

Example Hebrew HTML structure (single-page):

<!DOCTYPE html>
<html lang="he" dir="rtl">
<head>
  <meta charset="UTF-8">
  <link href="https://fonts.googleapis.com/css2?family=Heebo:wght@400;700&display=swap" rel="stylesheet">
  <style>
    @page { size: A4; margin: 0; }
    html, body {
      width: 210mm;
      height: 297mm;
      margin: 0;
      padding: 0;
      overflow: hidden;
    }
    .container {
      width: 100%;
      height: 100%;
      padding: 20mm;
      box-sizing: border-box;
      font-family: 'Heebo', sans-serif;
      direction: rtl;
      text-align: right;
      background: #f5f5f5; /* Background on container, NOT body */
    }
  </style>
</head>
<body>
  <div class="container">
    <h1>שלום עולם</h1>
    <p>זהו מסמך בעברית</p>
  </div>
</body>
</html>

CRITICAL: Always Use scale=1.0 for Multi-Page PDFs

NEVER use --scale < 1.0 for multi-page documents. It causes:

  • Content offset (not centered on page)
  • RTL text overflow/clipping in grid layouts
  • Unpredictable viewport width calculations

Instead: reduce CSS font sizes and spacing to fit content at scale=1.0.

.page {
  width: 210mm;         /* Matches A4 exactly at scale=1.0 */
  height: 297mm;        /* Matches A4 exactly at scale=1.0 */
  padding: 8mm 10mm 12mm;
  page-break-after: always;
  position: relative;
  background: #f7f8fa;

how to use html-to-pdf
How to use html-to-pdf on Cursor
AI-first code editor with Composer
1
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
  • ›Cursor installed and configured on your development machine
  • ›Node.js version 16.0+ with npm package manager (verify with node --version)
  • ›Active project directory or workspace where you want to add html-to-pdf
2
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
$npx skills add https://github.com/aviz85/claude-skills-library --skill html-to-pdf
The skills CLI fetches html-to-pdf from GitHub repository aviz85/claude-skills-library and configures it for Cursor.
3
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ── always included ────
│   • Amp
│   • Antigravity
│   • Cline
│   • Codex
│ ●Cursor(selected)
│   • Cursor
│   • Windsurf
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/html-to-pdf
Reload or restart Cursor to activate html-to-pdf. Access the skill through slash commands (e.g., /html-to-pdf) or your agent's skill management interface.
⚠
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
Additional Resources
›View source code on GitHub›Skills CLI documentation›Learn more about Cursor›What are agent skills?

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases▌

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

✓

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

✓

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

✓

Improve work quality by 30-40% with less effort

Implementation Guide▌

Prerequisites

  • ›Claude Desktop or compatible AI client with skill support
  • ›Clear understanding of task or problem to solve
  • ›Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • ⚠Expecting perfect results without iteration
  • ⚠Not providing enough context in prompts
  • ⚠Using skill for tasks outside its intended scope
  • ⚠Accepting outputs without review and validation

Best Practices▌

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • −Don't use without understanding skill limitations
  • −Don't skip validation of outputs
  • −Don't share sensitive information in prompts
  • −Don't expect skill to replace human judgment

💡 Pro Tips

  • ★Be specific about desired format and style
  • ★Ask for multiple options to choose from
  • ★Request explanations to understand reasoning
  • ★Combine AI efficiency with human expertise

When to Use This▌

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path▌

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.6★★★★★27 reviews
  • ★★★★★Dhruvi Jain· Dec 12, 2024

    Useful defaults in html-to-pdf — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • ★★★★★Nikhil Jackson· Dec 12, 2024

    I recommend html-to-pdf for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • ★★★★★Hana Thompson· Dec 8, 2024

    Keeps context tight: html-to-pdf is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • ★★★★★Anika Thompson· Nov 27, 2024

    Registry listing for html-to-pdf matched our evaluation — installs cleanly and behaves as described in the markdown.

  • ★★★★★Oshnikdeep· Nov 3, 2024

    html-to-pdf has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • ★★★★★Hana Okafor· Nov 3, 2024

    Solid pick for teams standardizing on skills: html-to-pdf is focused, and the summary matches what you get after install.

  • ★★★★★Ganesh Mohane· Oct 22, 2024

    Solid pick for teams standardizing on skills: html-to-pdf is focused, and the summary matches what you get after install.

  • ★★★★★Hana Sanchez· Oct 22, 2024

    html-to-pdf has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • ★★★★★Anika Tandon· Oct 18, 2024

    html-to-pdf reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • ★★★★★Rahul Santra· Sep 13, 2024

    We added html-to-pdf from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

showing 1-10 of 27

1 / 3