gsc-reportlisted

# Rendering a report Chat is the right medium for most answers. This skill is for the times it isn't: something to send a client, attach to a board pack, or keep as a record. **Analysis first, rendering second.** Never pull data straight into the template. Work the findings out with `gsc-seo-analysis` or `gsc-indexing-diagnostics`, decide what matters, and only then render. A beautifully typeset report that averages branded and non-branded CTR together is still wrong. ## What to produce One self-contained HTML file, written to the user's folder, built from `assets/report-template.html` in this plugin. It is designed so **Cmd-P → Save as PDF** produces a proper document — A4 page box, repeating table headers, no card or chart split across a page break. That is deliberately the whole PDF story: no headless Chromium, no WeasyPrint, no rendering dependency in the launcher that can break on someone's machine six months from now. Tell the user both things when you hand the file over: open it in a browser, and print to PDF if they need to send it. ## Brand Read the brand tokens from the site profile and paste them into the `:root` block. That is the only block that changes between sites. If the profile has no brand tokens, extract them first — the procedure is in the `gsc-site-profile` skill. It takes one browser call and is cached afterwards. If the site cannot be reached, fall back to the neutral defaults below and say plainly in your reply that the report is unbranded an