report-to-pdf

Convert static report exports into verified PDF artifacts with headless rendering.

1|2|Updated Jun 16, 2026
One-click install
npx skills add https://github.com/MuzeWinter/CooperAPI-Plugin --skill report-to-pdf-muzewinter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: report-to-pdf
Source: https://github.com/MuzeWinter/CooperAPI-Plugin/tree/main/plugins/data-analytics/skills/build-report/report-to-pdf
Command: npx skills add https://github.com/MuzeWinter/CooperAPI-Plugin --skill report-to-pdf-muzewinter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts an existing Data Analytics report, dashboard, or inline chart export into a verified PDF artifact when you need a portable, reviewable document instead of an interactive view.

Core Features & Use Cases

  • Static-source conversion: Uses a static HTML export or report file as the source of truth rather than a live app frame.
  • Headless PDF generation: Prints the static source with a browser-based renderer to preserve readable text, layout, charts, and tables.
  • Verification and repair: Checks page count, text extractability, and rendered pages to catch blank output, clipping, missing content, or unwanted app controls before handoff.
  • Use case: A reporting analyst can turn a completed dashboard export into a clean PDF for sharing with stakeholders, audits, or archival storage.

Quick Start

Convert the provided static report export into a verified PDF and return the PDF path, source path, and verification results.

Frequently Asked Questions about report-to-pdf

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a static HTML dashboard export to a PDF?

To convert a static HTML dashboard export to a PDF, this Skill uses a browser-based headless renderer like Chrome to print the source file, preserving readable text, charts, and tables into a portable document format.

What is PDF verification for report exports?

PDF verification for report exports is the process of checking the generated PDF for page count, selectable text extractability, and rendered page content to catch blank output, clipping, or missing charts before stakeholder handoff.

Can I use this to export an existing analytics report without a live app frame?

Yes, you can export an existing analytics report without a live app frame. The process specifically requires a static HTML export or report file as the source of truth rather than an interactive live application view.

Do I need Chrome headless rendering to generate verified PDF artifacts?

Yes, you need Chrome headless rendering or an equivalent local renderer to generate verified PDF artifacts. This browser-based printing mechanism is required to accurately preserve the layout and selectable text of the static source.

Why does my dashboard PDF export have missing content or unwanted app controls?

Dashboard PDF exports with missing content or unwanted app controls occur when rendering from a live app frame. Using a static HTML export as the source and applying page rendering inspection prevents clipping and removes interactive UI elements.

What is the best way to prepare analytics dashboards for archival storage?

The best way to prepare analytics dashboards for archival storage is to convert the static report file into a verified PDF artifact, ensuring selectable text checks pass and page rendering is clean for long-term document review.