Local html pdf reports

Skill zacharygcook/agent-skills/skills/local-html-pdf-reports

A curated collection of practical, evidence-backed skills for coding agents.

Install

npx -y skills add zacharygcook/agent-skills --skill local-html-pdf-reports

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

26 days oldThe repository was created 26 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Create polished local review artifacts as a Markdown source, self-contained HTML report, PDF, and rendered page images. Use for planning sheets, research summaries, run reports, probe results, or any disposable local document that benefits from visual review.

SKILL.md

2.5 KB, as published. Nobody here has run it

Local HTML and PDF Reports

Build a review folder containing a complete Markdown record, a designed self-contained HTML view, a PDF generated from that HTML, and page images used for visual verification.

Layout

notes/<topic>-<yyyy-mm-dd>/
  report.md
  report.html
  report.pdf
  render-check/
  command-output/   # optional raw evidence

Use the repository's preferred scratch location and naming when one exists. Do not promote disposable reports into tracked documentation without user approval.

Content Contract

Markdown is the complete evidence record: bottom line, scope, criteria, results, commands, artifacts, limitations, and next steps.
HTML is the designed review surface. It may be a concise executive view or a full-text review when the user needs to inspect every detail.
PDF must be regenerated after the final HTML edit.
Raw logs belong in separate files when they would overwhelm the report.

Design

Use a restrained print-friendly system: strong typographic hierarchy, high contrast, one intentional accent color, compact cards, readable tables, semantic status labels, and no external runtime dependencies. Add navigation/search or collapsible sections for long reports. Preserve accessibility, selectable text, and useful print behavior.

See references/style-guide.md for a reusable visual baseline. Adapt it to an established repository house style when one exists.

Generate and Verify

Format Markdown and HTML with repository-native tooling.
Print HTML to PDF with an installed browser using the intended page size and no browser headers/footers.
Inspect PDF metadata and page size.
Render every PDF page to an image.
Actually inspect the images for clipping, overflow, illegible code, broken tables, awkward page breaks, or nearly empty spill pages.
Fix, regenerate, and reinspect until clean.

Example tools include Chromium/Chrome headless printing, pdfinfo, and pdftoppm; discover installed commands rather than assuming exact paths.

Handoff

Open the HTML when the user requests local review and provide clickable absolute paths to the Markdown, HTML, and PDF. State the PDF page count and that rendered pages were visually checked.