| name | pro-report-builder |
| description | Create polished HTML technical reports and multi-page documents for consulting deliverables. Includes a customizable design system with dark cover page, warm cream content pages (8.5x11 portrait), professional typography, and a curated component library (KPI cards, data tables with severity coloring, callout boxes, recommendation cards, priority banners). Trigger on report, audit report, technical document, written report, assessment, or multi-page document. Outputs standalone HTML files exported to PDF via Chrome headless. |
| license | MIT |
| origin | custom |
| author | Rebecca Rae Barton |
| author_url | https://github.com/thatrebeccarae |
| metadata | {"version":"1.0.0","category":"reporting","domain":"consulting-deliverables","updated":"2026-03-18T00:00:00.000Z","tested":"2026-03-18T00:00:00.000Z","tested_with":"Claude Code v2.1"} |
Pro Report Builder
Polished consulting reports as standalone HTML. Export to PDF via Chrome headless.
Install
git clone https://github.com/thatrebeccarae/claude-marketing.git && cp -r claude-marketing/skills/pro-report-builder ~/.claude/skills/
Quick Reference
| Task | Approach |
|---|
| Create report from scratch | Read REFERENCE.md for CSS + HTML patterns |
| Add a new component type | Compose from existing components in REFERENCE.md |
| Export to PDF | Chrome headless --print-to-pdf (see Export section) |
| Customize brand tokens | Edit CSS custom properties in :root block |
When to Use This Skill vs pro-deck-builder
| pro-report-builder | pro-deck-builder |
|---|
| Format | 8.5x11" portrait pages | 16:9 landscape slides |
| Content flow | Multi-page, flowing text | Single-slide compositions |
| Export | Chrome headless --print-to-pdf | Puppeteer |
| Use for | Audit reports, assessments, written deliverables | Presentation decks, pitch slides |
Before You Start
Step 1: Understand the Brief
Ask the user:
- What type of document? Audit report, assessment, technical brief, case study?
- How many pages roughly? Helps plan section flow and page distribution.
- What data do they have? Raw numbers, API exports, spreadsheets? Pull exact values -- never estimate when actuals exist.
- Where should the file be saved? Default:
./output/
Step 2: Plan the Document Structure
Every report follows this structure:
Cover Page --> Executive Summary --> Analysis Sections (3-6) --> Prioritized Recommendations --> Quick Wins --> Appendix
