About this skill

What Problem It Addresses

Team reports often sit in scattered docs, spreadsheets, and meeting notes. Asking a model for Markdown or plain text usually misses layout, charts, and deliverable form; asking for HTML can introduce external dependencies, style drift, or output that does not match an expected visual system. This skill constrains report generation into a stable single-file workflow: provide data, receive an openable, shareable HTML page.

How It Works

It generates reports through a fixed pipeline:

Template selection: classify the input as weekly report, project progress, monthly summary, or postmortem, using references/templates.md as the structural guide.
Data extraction and completion: prefer user-provided data; if required fields are missing, ask only for required items and fill optional fields with reasonable defaults.
Self-contained HTML generation: inline all CSS in a <style> tag and render charts as inline SVG, including bar charts, line charts, and sparklines, avoiding external CSS/JS.
Design constraints: use warm ivory, oat, clay, olive, and sage variables; use serif headings, sans body text, and mono labels. Dark backgrounds, blue, pure black, pure red, heavy shadows, and all-sans designs are prohibited.
Delivery: save the generated file to the workspace, upload it to the user's cloud drive, and return a share link. Example templates include 01-weekly-report.html, 02-project-progress.html, 03-monthly-summary.html, and 04-postmortem.html.

Boundaries and Notes

This skill is best for structured reporting where conclusions and metrics already exist and a single-page deliverable is enough. It is not designed for highly open-ended content, complex interactive dashboards, live data sources, or full frontend applications. Because the output is a self-contained file, it is not a replacement for intranet pages that require login state, remote fonts, or external scripts. Chinese content should use lang="zh-CN" with an appropriate font stack, and output quality still depends on upstream data cleaning when headings, metrics, or narrative structure are incomplete.

Screenshots

Use Cases

Turn weekly team metrics and task status into a shareable weekly report HTML page.
Create a one-page project progress report covering milestones, risks, and current status.
Assemble monthly KPIs, root causes, and action items into a warm-toned summary page.
Write an incident postmortem with inline SVG timelines and impact metrics in one file.

Best For

Team leads who need to turn weekly metrics into a shareable one-page report.
Product managers who want project progress and risks presented in a fixed layout for leadership.
Engineers who need a fast postmortem page without hand-writing HTML.
Analysts who summarize monthly business metrics and need charts in self-contained HTML.