Is doc-to-pdf safe to install?

SaferSkills independently audited doc-to-pdf (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

doc-to-pdf/SKILL.md · 1 file

doc-to-pdf/SKILL.md1.9 KB · Markdown

name: doc-to-pdf

description: Render a Markdown or HTML document into a clean, branded, multi-page PDF via headless Chrome — the polished deliverable you'd hand a client, not a screenshot. Brand wrap (print-CSS + footer) is on by default; --no-brand for raw; --template for a custom shell. Never overwrites without --force. Use when the user says "make a PDF", "turn this into a PDF", "PDF this", "send them a PDF", "build a client doc", "export to PDF", "branded PDF".

doc-to-pdf

One command from a Markdown or HTML file to a presentation-grade PDF. Uses headless Chrome's --print-to-pdf (best-fidelity HTML→PDF on a normal machine) and wraps your content in a consistent brand template so every client deliverable matches.

When to use

Turning a Markdown brief or an HTML page into a client-ready PDF
Producing a branded workflow/roadmap/proposal document
Any "send them a PDF" moment where it should look intentional

How it works

Markdown input → HTML (python-markdown, falling back to pandoc, then a minimal converter).
HTML input → used as-is.
Wraps in the brand template (letter page, print margins, blue accents, footer) unless --no-brand.
Renders via headless Chrome (--headless=new --no-pdf-header-footer).

CLI

python3 doc_to_pdf.py <input.md|input.html> [-o out.pdf] [--title "..."] [--no-brand] [--template tpl.html] [--force]

Examples:

python3 doc_to_pdf.py roadmap.md -o "Brothers - Roadmap.pdf" --title "Brothers Composites — Roadmap"
python3 doc_to_pdf.py hub.html --no-brand        # already-styled HTML, no wrap

Safety

Produces a new file; never overwrites an existing PDF without --force.
No network, no credentials.
Requires Chrome / Chromium / Edge installed (any one).

doc-to-pdf— agent skill

Is doc-to-pdf safe to install?

doc-to-pdf

When to use

How it works

CLI

Safety

See also

Audit the pieces. Scan the whole. Decide.