report-pagelisted

# Report Page ## Overview Build a report or document that reads like the kind of deliverable the user actually asked for: clear narrative sections, calm typography, useful blocks, optional source-backed evidence, optional quantitative figures rendered through ECharts, tables, images, diagrams, captions, and a dynamic side table of contents. Static HTML is the delivery format, not the purpose of the skill. This skill is for document-style outputs across many domains: research reports, strategy memos, company/market briefs, technical or product notes, operating updates, data interpretation pages, analytical readouts, and long-form source-backed writing. It is especially useful when the user needs evidence, narrative interpretation, and readable charts/tables in one self-contained document. It is not primarily a dashboard skill, slide skill, landing-page builder, marketing site builder, or app framework. Default to a hand-authored static `index.html` with lightweight external assets: `assets/doc.css`, `assets/doc.js`, `assets/mermaid.min.js` when Mermaid diagrams are present, and `assets/echarts.min.js` only when quantitative charts are present. Do not create a Python generator. The document should be easy for an AI or human to edit directly. Keep the mental model simple: the page is the source of truth. Use HTML document blocks, not a hidden generator, CMS schema, or app runtime. The document components are tools, not a layout recipe. Do not default to summary -> metrics