Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

Começar

beautiful-pdfs

Estrelas217

Forks9

Atualizado6 de julho de 2026 às 17:45

Build polished PDF documents by composing semantic HTML/CSS and rendering HTML to PDF.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

aduermael

aduermael/herm

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Editores de desktopEscritório e Suporte Administrativo·SOC 43-9031

Explorador de arquivos

2 arquivos

SKILL.md

readonly

name	beautiful-pdfs
description	Build polished PDF documents by composing semantic HTML/CSS and rendering HTML to PDF.
metadata	{"short-description":"Build polished PDFs with HTML and CSS"}

Beautiful PDFs

Use this skill when the user asks for a PDF, printable report, invoice, brief, handout, form, one-pager, or visual document.

Workflow

Use the available Luau globals directly. Do not call require; use fs.read, fs.write, and doc.renderFile.

Confirm HTML-to-PDF rendering is available before investing in a long document. If unsure, create a tiny HTML file in /tmp and run:

fs.write("/tmp/pdf-smoke.html", "<!doctype html><meta charset=\"utf-8\"><h1>PDF smoke test</h1>")
doc.renderFile({source="/tmp/pdf-smoke.html", target="/tmp/pdf-smoke.pdf"})
print(fs.exists("/tmp/pdf-smoke.pdf"))

If rendering reports platform not supported, policy denial, or another capability error, stop PDF-generation work. Tell the user that PDF creation is unavailable in this session; do not try image-based PDF, font fetching, network downloads, package installs, browser printing, external renderers, or OS tools.
Create semantic HTML. Use real document structure: headings, sections, tables, figures, captions, footers, and page-break rules.
Put presentation in CSS. Prefer restrained typography, clear spacing, durable contrast, and print-safe colors. Avoid huge hero layouts unless the user explicitly asks for a cover page.
Write source HTML to a temporary or hidden build path unless the user explicitly asks for editable source files.
Render HTML to PDF with the available document module. Start by checking help() and doc.help() if the exact API is not already visible in context.
Prefer doc.renderFile({source="/tmp/report.html", target="/home/herm/report.pdf"}) for saved HTML-to-PDF output. It detects html -> pdf from the file extensions.
Inspect the resulting PDF metadata or page count when practical before telling the user it is ready.

Luau Snippets

Read and adapt the bundled print baseline when useful:

local css = fs.read("/skills/beautiful-pdfs/print.css")

Build source HTML in /tmp so the user only sees the PDF unless they ask for source files:

local css = fs.read("/skills/beautiful-pdfs/print.css")
local html = [[
<!doctype html>
<html>
<head>
  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width, initial-scale=1">
  <style>]] .. css .. [[</style>
</head>
<body>
  <main class="page">
    <h1>Document Title</h1>
    <p>Replace this with the user's content.</p>
  </main>
</body>
</html>
]]

fs.write("/tmp/report.html", html)

Render the temporary HTML to the durable PDF path and verify that it exists:

doc.renderFile({source="/tmp/report.html", target="/home/herm/report.pdf"})
print(fs.exists("/home/herm/report.pdf"))

HTML Guidance

print.css contains a compact print-oriented baseline you can read and adapt when useful.
Include <!doctype html>, <meta charset="utf-8">, and a viewport meta tag.
Add @page rules for size and margins. Use letter size unless the user asks for another page size.
Add deliberate page breaks for multipage documents. Use .page for fixed page-sized sections, break-before: page for major section starts, and break-after: page for cover/title pages.
Use CSS variables for palette and spacing so revisions are easy.
Keep cards and panels print-friendly: subtle borders, no heavy shadows, no fragile fixed viewport heights.
Use break-inside: avoid only on content that must stay together, such as figures, callouts, short tables, signatures, and compact sections. Do not apply it to long sections or large tables that may need to span pages.

Output

When rendering succeeds, save the PDF under /home/herm unless the user requested another path. If the user asked only for a PDF, expose only the PDF in the final response; do not place or present source HTML next to it. Keep source files in /tmp or a hidden build directory unless the user asks for editable source files.

When rendering fails, do not claim a PDF was created. Preserve polished HTML only if useful, and say clearly that no PDF was produced in this session.

Mais deste repositório

mesmo repositório

image-vision

aduermael/herm

Inspect attached or local images and visually analyze PDFs with CPSL vision. Use for photos, screenshots, scans, charts, diagrams, OCR, handwriting, UI inspection, or any task that depends on pixels, layout, or other non-structural page content.

2026-07-14217

apple-context

aduermael/herm

Use CPSL calendar and location modules for user-approved Apple Calendar events and current device location.

2026-07-12217

webbrowser

aduermael/herm

Use CPSL's native webbrowser module for web search, browsing, authenticated website interaction, forms, file uploads and downloads, screenshots, and user handoff.

2026-07-12217

c-bounds-safety

aduermael/herm

Guide for the C -fbounds-safety language extension. Covers the language model, pointer annotations, adopting bounds-safety in existing C code, compiler build settings and modes, and runtime debugging of bounds violations.

2026-06-30217

device-interaction

aduermael/herm

Verify iOS app behavior on device or simulator via screenshots, UI hierarchy, and touch interactions.

2026-06-30217

modernize-tests

aduermael/herm

Modernize test suites to use modern Swift Testing features or migrate from XCTest.

2026-06-30217

Beautiful PDFs

Use this skill when the user asks for a PDF, printable report, invoice, brief, handout, form, one-pager, or visual document.

Workflow

Use the available Luau globals directly. Do not call require; use fs.read, fs.write, and doc.renderFile.

Confirm HTML-to-PDF rendering is available before investing in a long document. If unsure, create a tiny HTML file in /tmp and run:

fs.write("/tmp/pdf-smoke.html", "<!doctype html><meta charset=\"utf-8\"><h1>PDF smoke test</h1>")
doc.renderFile({source="/tmp/pdf-smoke.html", target="/tmp/pdf-smoke.pdf"})
print(fs.exists("/tmp/pdf-smoke.pdf"))

If rendering reports platform not supported, policy denial, or another capability error, stop PDF-generation work. Tell the user that PDF creation is unavailable in this session; do not try image-based PDF, font fetching, network downloads, package installs, browser printing, external renderers, or OS tools.

Create semantic HTML. Use real document structure: headings, sections, tables, figures, captions, footers, and page-break rules.

Put presentation in CSS. Prefer restrained typography, clear spacing, durable contrast, and print-safe colors. Avoid huge hero layouts unless the user explicitly asks for a cover page.

Write source HTML to a temporary or hidden build path unless the user explicitly asks for editable source files.

Render HTML to PDF with the available document module. Start by checking help() and doc.help() if the exact API is not already visible in context.

Prefer doc.renderFile({source="/tmp/report.html", target="/home/herm/report.pdf"}) for saved HTML-to-PDF output. It detects html -> pdf from the file extensions.

Inspect the resulting PDF metadata or page count when practical before telling the user it is ready.

Luau Snippets

Read and adapt the bundled print baseline when useful:

local css = fs.read("/skills/beautiful-pdfs/print.css")

Build source HTML in /tmp so the user only sees the PDF unless they ask for source files:

local css = fs.read("/skills/beautiful-pdfs/print.css") local html = [[ <!doctype html> <html> <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width, initial-scale=1"> <style>]] .. css .. [[</style> </head> <body> <main class="page"> <h1>Document Title</h1> <p>Replace this with the user's content.</p> </main> </body> </html> ]] fs.write("/tmp/report.html", html)

Render the temporary HTML to the durable PDF path and verify that it exists:

doc.renderFile({source="/tmp/report.html", target="/home/herm/report.pdf"}) print(fs.exists("/home/herm/report.pdf"))

HTML Guidance

print.css contains a compact print-oriented baseline you can read and adapt when useful.

Include <!doctype html>, <meta charset="utf-8">, and a viewport meta tag.

Add @page rules for size and margins. Use letter size unless the user asks for another page size.

Add deliberate page breaks for multipage documents. Use .page for fixed page-sized sections, break-before: page for major section starts, and break-after: page for cover/title pages.

Use CSS variables for palette and spacing so revisions are easy.

Keep cards and panels print-friendly: subtle borders, no heavy shadows, no fragile fixed viewport heights.

Use break-inside: avoid only on content that must stay together, such as figures, callouts, short tables, signatures, and compact sections. Do not apply it to long sections or large tables that may need to span pages.

Output

When rendering fails, do not claim a PDF was created. Preserve polished HTML only if useful, and say clearly that no PDF was produced in this session.